Evidence-based healthcare information management protocols

ABSTRACT

Structures and protocols are presented for signaling a status or decision (processing or transmitting a medical record or other resource, e.g.) conditionally. Such signaling may be partly based on one or more symptoms, regimen attributes, performance indicia (compliance indications, e.g.), privacy considerations (patient consent, e.g.), contextual considerations (being in or admitted by a care facility, e.g.), sensor data, or other such determinants. In some contexts this may trigger an incentive being manifested (as a dispensation of an item, e.g.), an intercommunication (telephone call, e.g.) beginning, a device being configured (enabled or customized, e.g.), data distillations being presented or tracked, or other such results.

If an Application Data Sheet (ADS) has been filed on the filing date ofthis application, it is incorporated by reference herein. Anyapplications claimed on the ADS for priority under 35 U.S.C. §§ 119,120, 121, or 365(c), and any and all parent, grandparent,great-grandparent, etc. applications of such applications, are alsoincorporated by reference, including any priority claims made in thoseapplications and any material incorporated by reference, to the extentsuch subject matter is not inconsistent herewith.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is related to and/or claims the benefit of theearliest available effective filing date(s) from the following listedapplication(s) (the “Priority Applications”), if any, listed below(e.g., claims earliest available priority dates for other thanprovisional patent applications or claims benefits under 35 USC § 119(e)for provisional patent applications, for any and all parent,grandparent, great-grandparent, etc. applications of the PriorityApplication(s)). In addition, the present application is related to the“Related Applications,” if any, listed below.

PRIORITY APPLICATIONS

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 13/374,519, entitled EVIDENCE-BASED HEALTHCAREINFORMATION MANAGEMENT PROTOCOLS, naming Roderick A. Hyde; Edward K. Y.Jung; Jordin T. Kare; Eric C. Leuthardt; Royce A. Levien; Richard T.Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Dennis J.Rivet; Clarence T. Tegreene; and Lowell L. Wood, Jr. as inventors, filed30 Dec. 2011 with, which is currently co-pending or is an application ofwhich a currently co-pending application is entitled to the benefit ofthe filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 13/374,747, entitled EVIDENCE-BASED HEALTHCAREINFORMATION MANAGEMENT PROTOCOLS, naming Roderick A. Hyde; Edward K. Y.Jung; Jordin T. Kare; Eric C. Leuthardt; Royce A. Levien; Richard T.Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Dennis J.Rivet; Clarence T. Tegreene; and Lowell L. Wood, Jr. as inventors, filed9 Jan. 2012 with, which is currently co-pending or is an application ofwhich a currently co-pending application is entitled to the benefit ofthe filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 13/374,750, entitled EVIDENCE-BASED HEALTHCAREINFORMATION MANAGEMENT PROTOCOLS, naming Roderick A. Hyde; Edward K. Y.Jung; Jordin T. Kare; Eric C. Leuthardt; Royce A. Levien; Richard T.Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Dennis J.Rivet; Clarence T. Tegreene; and Lowell L. Wood, Jr. as inventors, filed9 Jan. 2012 with, which is currently co-pending or is an application ofwhich a currently co-pending application is entitled to the benefit ofthe filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 13/374,745, entitled EVIDENCE-BASED HEALTHCAREINFORMATION MANAGEMENT PROTOCOLS, naming Roderick A. Hyde; Edward K. Y.Jung; Jordin T. Kare; Eric C. Leuthardt; Royce A. Levien; Richard T.Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Dennis J.Rivet; Clarence T. Tegreene; and Lowell L. Wood, Jr. as inventors, filed9 Jan. 2012 with, which is currently co-pending or is an application ofwhich a currently co-pending application is entitled to the benefit ofthe filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 13/374,744, entitled EVIDENCE-BASED HEALTHCAREINFORMATION MANAGEMENT PROTOCOLS, naming Roderick A. Hyde; Edward K. Y.Jung; Jordin T. Kare; Eric C. Leuthardt; Royce A. Levien; Richard T.Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Dennis J.Rivet; Clarence T. Tegreene; and Lowell L. Wood, Jr. as inventors, filed9 Jan. 2012 with, which is currently co-pending or is an application ofwhich a currently co-pending application is entitled to the benefit ofthe filing date.

For purposes of the USPTO extra-statutory requirements, the presentapplication constitutes a continuation-in-part of U.S. patentapplication Ser. No. 13/374,748, entitled EVIDENCE-BASED HEALTHCAREINFORMATION MANAGEMENT PROTOCOLS, naming Roderick A. Hyde; Edward K. Y.Jung; Jordin T. Kare; Eric C. Leuthardt; Royce A. Levien; Richard T.Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.; Dennis J.Rivet; Clarence T. Tegreene; and Lowell L. Wood, Jr. as inventors, filed9 Jan. 2012 with, which is currently co-pending or is an application ofwhich a currently co-pending application is entitled to the benefit ofthe filing date.

RELATED APPLICATIONS

U.S. patent application Ser. No. 13/705,311, entitled EVIDENCE-BASEDHEALTHCARE INFORMATION MANAGEMENT PROTOCOLS, naming Roderick A. Hyde;Edward K. Y. Jung; Jordin T. Kare; Eric C. Leuthardt; Royce A. Levien;Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.;Dennis J. Rivet; Clarence T. Tegreene; and Lowell L. Wood, Jr. asinventors, filed on even date herewith, is related to the presentapplication.

U.S. patent application Ser. No. 13/705,327, entitled EVIDENCE-BASEDHEALTHCARE INFORMATION MANAGEMENT PROTOCOLS, naming Roderick A. Hyde;Edward K. Y. Jung; Jordin T. Kare; Eric C. Leuthardt; Royce A. Levien;Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.;Dennis J. Rivet; Clarence T. Tegreene; and Lowell L. Wood, Jr. asinventors, filed on even date herewith, is related to the presentapplication.

U.S. patent application Ser. No. 13/705,338, entitled EVIDENCE-BASEDHEALTHCARE INFORMATION MANAGEMENT PROTOCOLS, naming Roderick A. Hyde;Edward K. Y. Jung; Jordin T. Kare; Eric C. Leuthardt; Royce A. Levien;Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.;Dennis J. Rivet; Clarence T. Tegreene; and Lowell L. Wood, Jr. asinventors, filed on even date herewith, is related to the presentapplication.

U.S. patent application Ser. No. 13/705,347, entitled EVIDENCE-BASEDHEALTHCARE INFORMATION MANAGEMENT PROTOCOLS, naming Roderick A. Hyde;Edward K. Y. Jung; Jordin T. Kare; Eric C. Leuthardt; Royce A. Levien;Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.;Dennis J. Rivet; Clarence T. Tegreene; and Lowell L. Wood, Jr. asinventors, filed on even date herewith, is related to the presentapplication.

U.S. patent application Ser. No. 13/705,365, entitled EVIDENCE-BASEDHEALTHCARE INFORMATION MANAGEMENT PROTOCOLS, naming Roderick A. Hyde;Edward K. Y. Jung; Jordin T. Kare; Eric C. Leuthardt; Royce A. Levien;Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.;Dennis J. Rivet; Clarence T. Tegreene; and Lowell L. Wood, Jr. asinventors, filed on even date herewith, is related to the presentapplication.

U.S. patent application Ser. No. 13/705,379, entitled EVIDENCE-BASEDHEALTHCARE INFORMATION MANAGEMENT PROTOCOLS, naming Roderick A. Hyde;Edward K. Y. Jung; Jordin T. Kare; Eric C. Leuthardt; Royce A. Levien;Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.;Dennis J. Rivet; Clarence T. Tegreene; and Lowell L. Wood, Jr. asinventors, filed on even date herewith, is related to the presentapplication.

U.S. patent application Ser. No. 13/705,390 , entitled EVIDENCE-BASEDHEALTHCARE INFORMATION MANAGEMENT PROTOCOLS, naming Roderick A. Hyde;Edward K. Y. Jung; Jordin T. Kare; Eric C. Leuthardt; Royce A. Levien;Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.;Dennis J. Rivet; Clarence T. Tegreene; and Lowell L. Wood, Jr. asinventors, filed on even date herewith, is related to the presentapplication.

U.S. patent application Ser. No. 13/705,402, entitled EVIDENCE-BASEDHEALTHCARE INFORMATION MANAGEMENT PROTOCOLS, naming Roderick A. Hyde;Edward K. Y. Jung; Jordin T. Kare; Eric C. Leuthardt; Royce A. Levien;Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.;Dennis J. Rivet; Clarence T. Tegreene; and Lowell L. Wood, Jr. asinventors, filed on even date herewith, is related to the presentapplication.

U.S. patent application Ser. No. 13/705,421, entitled EVIDENCE-BASEDHEALTHCARE INFORMATION MANAGEMENT PROTOCOLS, naming Roderick A. Hyde;Edward K. Y. Jung; Jordin T. Kare; Eric C. Leuthardt; Royce A. Levien;Richard T. Lord; Robert W. Lord; Mark A. Malamud; John D. Rinaldo, Jr.;Dennis J. Rivet; Clarence T. Tegreene; and Lowell L. Wood, Jr. asinventors, filed on even date herewith, is related to the presentapplication.

The United States Patent Office (USPTO) has published a notice to theeffect that the USPTO's computer programs require that patent applicantsreference both a serial number and indicate whether an application is acontinuation, continuation-in-part, or divisional of a parentapplication. Stephen G. Kunin, Benefit of Prior-Filed Application, USPTOOfficial Gazette Mar. 18, 2003. The USPTO further has provided forms forthe Application Data Sheet which allow automatic loading ofbibliographic data but which require identification of each applicationas a continuation, continuation-in-part, or divisional of a parentapplication. The present Applicant Entity (hereinafter “Applicant”) hasprovided above a specific reference to the application(s) from whichpriority is being claimed as recited by statute. Applicant understandsthat the statute is unambiguous in its specific reference language anddoes not require either a serial number or any characterization, such as“continuation” or “continuation-in-part,” for claiming priority to U.S.patent applications. Notwithstanding the foregoing, Applicantunderstands that the USPTO's computer programs have certain data entryrequirements, and hence Applicant has provided designation(s) of arelationship between the present application and its parentapplication(s) as set forth above and in any ADS filed in thisapplication, but expressly points out that such designation(s) are notto be construed in any way as any type of commentary and/or admission asto whether or not the present application contains any new matter inaddition to the matter of its parent application(s).

If the listings of applications provided above are inconsistent with thelistings provided via an ADS, it is the intent of the Applicant to claimpriority to each application that appears in the Priority Applicationssection of the ADS and to each application that appears in the PriorityApplications section of this application.

All subject matter of the Priority Applications and the RelatedApplications and of any and all parent, grandparent, great-grandparent,etc. applications of the Priority Applications and the RelatedApplications, including any priority claims, is incorporated herein byreference to the extent such subject matter is not inconsistentherewith.

TECHNICAL FIELD

This disclosure relates to managing information in an evidence-basedmedical practice, particularly records of patients and treatments.

SUMMARY

An embodiment provides a method. In one implementation, the methodincludes but is not limited to causing an electronic record of a firstprotocol (comprising one or more instances of diagnostic evaluations,regimen implementations, or medical interventions, e.g.) for aparticular condition (comprising one or more instances of injuries,complaints, or pathologies, e.g.) to be annotated with a scan of adocument and retrieving the electronic record of the first protocolafter the electronic record of the first protocol is annotated with thescan of the document partly based on an indication of a first patientundergoing the first protocol and partly based on an indication of aninstitutional readmission. In addition to the foregoing, other methodaspects are described in the claims, drawings, and text forming a partof the present disclosure.

In one or more various aspects, related machines, compositions ofmatter, or manufactures of systems may include virtually any combinationpermissible under 35 U.S.C. § 101 of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for causing an electronicrecord of a first protocol for a particular condition to be annotatedwith a scan of a document and circuitry for retrieving the electronicrecord of the first protocol after the electronic record of the firstprotocol is annotated with the scan of the document partly based on anindication of a first patient undergoing the first protocol and partlybased on an indication of an institutional readmission. In addition tothe foregoing, other system aspects are described in the claims,drawings, and text forming a part of the present disclosure.

An embodiment provides an article of manufacture including a computerprogram product. In one implementation, the article of manufactureincludes but is not limited to a signal-bearing medium configured by oneor more instructions related to causing an electronic record of a firstprotocol for a particular condition to be annotated with a scan of adocument and retrieving the electronic record of the first protocolafter the electronic record of the first protocol is annotated with thescan of the document partly based on an indication of a first patientundergoing the first protocol and partly based on an indication of aninstitutional readmission. In addition to the foregoing, other computerprogram product aspects are described in the claims, drawings, and textforming a part of the present disclosure.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to a computing device and instructions. Theinstructions when executed on the computing device configure thecomputing device for causing an electronic record of a first protocolfor a particular condition to be annotated with a scan of a document andretrieving the electronic record of the first protocol after theelectronic record of the first protocol is annotated with the scan ofthe document partly based on an indication of a first patient undergoingthe first protocol and partly based on an indication of an institutionalreadmission. In addition to the foregoing, other system aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

An embodiment provides a method. In one implementation, the methodincludes but is not limited to obtaining an indication that a particularcondition was treated in a first patient with a first protocol; causinga record of a second patient to include the indication that theparticular condition was treated in the first patient with the firstprotocol; and retrieving the record of the second patient selectively inresponse to an association between the second patient and an indicationof an institutional readmission after the record of the second patientincludes the indication that the particular condition was treated in thefirst patient with the first protocol. In addition to the foregoing,other method aspects are described in the claims, drawings, and textforming a part of the present disclosure.

In one or more various aspects, related machines, compositions ofmatter, or manufactures of systems may include virtually any combinationpermissible under 35 U.S.C. § 101 of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for obtaining an indicationthat a particular condition was treated in a first patient with a firstprotocol; circuitry for causing a record of a second patient to includethe indication that the particular condition was treated in the firstpatient with the first protocol; and circuitry for retrieving the recordof the second patient selectively in response to an association betweenthe second patient and an indication of an institutional readmissionafter the record of the second patient includes the indication that theparticular condition was treated in the first patient with the firstprotocol. In addition to the foregoing, other system aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

An embodiment provides an article of manufacture including a computerprogram product. In one implementation, the article of manufactureincludes but is not limited to a signal-bearing medium configured by oneor more instructions related to obtaining an indication that aparticular condition was treated in a first patient with a firstprotocol; causing a record of a second patient to include the indicationthat the particular condition was treated in the first patient with thefirst protocol; and retrieving the record of the second patientselectively in response to an association between the second patient andan indication of an institutional readmission after the record of thesecond patient includes the indication that the particular condition wastreated in the first patient with the first protocol. In addition to theforegoing, other computer program product aspects are described in theclaims, drawings, and text forming a part of the present disclosure.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to a computing device and instructions. Theinstructions when executed on the computing device configure thecomputing device for obtaining an indication that a particular conditionwas treated in a first patient with a first protocol; causing a recordof a second patient to include the indication that the particularcondition was treated in the first patient with the first protocol; andretrieving the record of the second patient selectively in response toan association between the second patient and an indication of aninstitutional readmission after the record of the second patientincludes the indication that the particular condition was treated in thefirst patient with the first protocol. In addition to the foregoing,other system aspects are described in the claims, drawings, and textforming a part of the present disclosure.

An embodiment provides a method. In one implementation, the methodincludes but is not limited to obtaining an indication of a firstprotocol being employed in relation to a particular condition in a firstpatient; requesting an effectiveness indication of the first protocolfrom an entity partly based on the entity validating the first protocoland partly based on a first communication delay associated with thefirst protocol, the first communication delay exceeding one hour; andsignaling a decision whether to update a prominence indication of thefirst protocol in response to whether the effectiveness indication ofthe first protocol was received from the entity after the effectivenessindication is requested from the entity partly based on the entityvalidating the first protocol and partly based on the firstcommunication delay associated with the first protocol. In addition tothe foregoing, other method aspects are described in the claims,drawings, and text forming a part of the present disclosure.

In one or more various aspects, related machines, compositions ofmatter, or manufactures of systems may include virtually any combinationpermissible under 35 U.S.C. § 101 of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for obtaining an indication ofa first protocol being employed in relation to a particular condition ina first patient; circuitry for requesting an effectiveness indication ofthe first protocol from an entity partly based on the entity validatingthe first protocol and partly based on a first communication delayassociated with the first protocol, the first communication delayexceeding one hour; and circuitry for signaling a decision whether toupdate a prominence indication of the first protocol in response towhether the effectiveness indication of the first protocol was receivedfrom the entity after the effectiveness indication is requested from theentity partly based on the entity validating the first protocol andpartly based on the first communication delay associated with the firstprotocol. In addition to the foregoing, other system aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

An embodiment provides an article of manufacture including a computerprogram product. In one implementation, the article of manufactureincludes but is not limited to a signal-bearing medium configured by oneor more instructions related to obtaining an indication of a firstprotocol being employed in relation to a particular condition in a firstpatient; requesting an effectiveness indication of the first protocolfrom an entity partly based on the entity validating the first protocoland partly based on a first communication delay associated with thefirst protocol, the first communication delay exceeding one hour; andsignaling a decision whether to update a prominence indication of thefirst protocol in response to whether the effectiveness indication ofthe first protocol was received from the entity after the effectivenessindication is requested from the entity partly based on the entityvalidating the first protocol and partly based on the firstcommunication delay associated with the first protocol. In addition tothe foregoing, other computer program product aspects are described inthe claims, drawings, and text forming a part of the present disclosure.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to a computing device and instructions. Theinstructions when executed on the computing device configure thecomputing device for obtaining an indication of a first protocol beingemployed in relation to a particular condition in a first patient;requesting an effectiveness indication of the first protocol from anentity partly based on the entity validating the first protocol andpartly based on a first communication delay associated with the firstprotocol, the first communication delay exceeding one hour; andsignaling a decision whether to update a prominence indication of thefirst protocol in response to whether the effectiveness indication ofthe first protocol was received from the entity after the effectivenessindication is requested from the entity partly based on the entityvalidating the first protocol and partly based on the firstcommunication delay associated with the first protocol. In addition tothe foregoing, other system aspects are described in the claims,drawings, and text forming a part of the present disclosure.

An embodiment provides a method. In one implementation, the methodincludes but is not limited to obtaining an association between aparticular condition and a first protocol; causing a comparison betweena threshold and a prominence indication of treating the particularcondition with the first protocol after the association between thenparticular condition and the first protocol is obtained; and signaling adecision whether to caution a caregiver partly based on the associationbetween the particular condition and the first protocol and partly basedon the comparison between the threshold and the prominence indication oftreating the particular condition with the first protocol. In additionto the foregoing, other method aspects are described in the claims,drawings, and text forming a part of the present disclosure.

In one or more various aspects, related machines, compositions ofmatter, or manufactures of systems may include virtually any combinationpermissible under 35 U.S.C. § 101 of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for obtaining an associationbetween a particular condition and a first protocol; circuitry forcausing a comparison between a threshold and a prominence indication oftreating the particular condition with the first protocol after theassociation between then particular condition and the first protocol isobtained; and circuitry for signaling a decision whether to caution acaregiver partly based on the association between the particularcondition and the first protocol and partly based on the comparisonbetween the threshold and the prominence indication of treating theparticular condition with the first protocol. In addition to theforegoing, other system aspects are described in the claims, drawings,and text forming a part of the present disclosure.

An embodiment provides an article of manufacture including a computerprogram product. In one implementation, the article of manufactureincludes but is not limited to a signal-bearing medium configured by oneor more instructions related to obtaining an association between aparticular condition and a first protocol; causing a comparison betweena threshold and a prominence indication of treating the particularcondition with the first protocol after the association between thenparticular condition and the first protocol is obtained; and signaling adecision whether to caution a caregiver partly based on the associationbetween the particular condition and the first protocol and partly basedon the comparison between the threshold and the prominence indication oftreating the particular condition with the first protocol. In additionto the foregoing, other computer program product aspects are describedin the claims, drawings, and text forming a part of the presentdisclosure.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to a computing device and instructions. Theinstructions when executed on the computing device configure thecomputing device for obtaining an association between a particularcondition and a first protocol; causing a comparison between a thresholdand a prominence indication of treating the particular condition withthe first protocol after the association between then particularcondition and the first protocol is obtained; and signaling a decisionwhether to caution a caregiver partly based on the association betweenthe particular condition and the first protocol and partly based on thecomparison between the threshold and the prominence indication oftreating the particular condition with the first protocol. In additionto the foregoing, other system aspects are described in the claims,drawings, and text forming a part of the present disclosure.

An embodiment provides a method. In one implementation, the methodincludes but is not limited to obtaining an association between a careadministration space and a first device; obtaining via a second device apatient consent conditionally authorizing a release of a first medicalrecord, the second device being a mobile device; and causing the firstdevice to receive the first medical record partly based on the seconddevice entering the care administration space and partly based on thepatient consent authorizing the release of the first medical record. Inaddition to the foregoing, other method aspects are described in theclaims, drawings, and text forming a part of the present disclosure.

In one or more various aspects, related machines, compositions ofmatter, or manufactures of systems may include virtually any combinationpermissible under 35 U.S.C. § 101 of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for obtaining an associationbetween a care administration space and a first device; circuitry forobtaining via a second device a patient consent conditionallyauthorizing a release of a first medical record, the second device beinga mobile device; and circuitry for causing the first device to receivethe first medical record partly based on the second device entering thecare administration space and partly based on the patient consentauthorizing the release of the first medical record. In addition to theforegoing, other system aspects are described in the claims, drawings,and text forming a part of the present disclosure.

An embodiment provides an article of manufacture including a computerprogram product. In one implementation, the article of manufactureincludes but is not limited to a signal-bearing medium configured by oneor more instructions related to obtaining an association between a careadministration space and a first device; obtaining via a second device apatient consent conditionally authorizing a release of a first medicalrecord, the second device being a mobile device; and causing the firstdevice to receive the first medical record partly based on the seconddevice entering the care administration space and partly based on thepatient consent authorizing the release of the first medical record. Inaddition to the foregoing, other computer program product aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to a computing device and instructions. Theinstructions when executed on the computing device configure thecomputing device for obtaining an association between a careadministration space and a first device; obtaining via a second device apatient consent conditionally authorizing a release of a first medicalrecord, the second device being a mobile device; and causing the firstdevice to receive the first medical record partly based on the seconddevice entering the care administration space and partly based on thepatient consent authorizing the release of the first medical record. Inaddition to the foregoing, other system aspects are described in theclaims, drawings, and text forming a part of the present disclosure.

An embodiment provides a method. In one implementation, the methodincludes but is not limited to obtaining an indication of a first deviceassociated with and wearable by a patient hospitalized for a particularcondition; obtaining an indication of a second device associated withand wearable by a caregiver; causing a recordation of a timestamp as anautomatic response to the first device associated with and wearable bythe patient and the second device associated with and wearable by acaregiver both being in a single common location; and describes causinga retrieval of the timestamp in response to an indication of aninstitutional readmission after the recordation of the timestampindicating the first device associated with and wearable by the patientand the second device associated with and wearable by the caregiver bothhaving been in the single common location. In addition to the foregoing,other method aspects are described in the claims, drawings, and textforming a part of the present disclosure.

In one or more various aspects, related machines, compositions ofmatter, or manufactures of systems may include virtually any combinationpermissible under 35 U.S.C. § 101 of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for obtaining an indication ofa first device associated with and wearable by a patient hospitalizedfor a particular condition; obtaining an indication of a second deviceassociated with and wearable by a caregiver; causing a recordation of atimestamp as an automatic response to the first device associated withand wearable by the patient and the second device associated with andwearable by a caregiver both being in a single common location; anddescribes causing a retrieval of the timestamp in response to anindication of an institutional readmission after the recordation of thetimestamp indicating the first device associated with and wearable bythe patient and the second device associated with and wearable by thecaregiver both having been in the single common location. In addition tothe foregoing, other system aspects are described in the claims,drawings, and text forming a part of the present disclosure.

An embodiment provides an article of manufacture including a computerprogram product. In one implementation, the article of manufactureincludes but is not limited to a signal-bearing medium configured by oneor more instructions related to obtaining an indication of a firstdevice associated with and wearable by a patient hospitalized for aparticular condition; obtaining an indication of a second deviceassociated with and wearable by a caregiver; causing a recordation of atimestamp as an automatic response to the first device associated withand wearable by the patient and the second device associated with andwearable by a caregiver both being in a single common location; anddescribes causing a retrieval of the timestamp in response to anindication of an institutional readmission after the recordation of thetimestamp indicating the first device associated with and wearable bythe patient and the second device associated with and wearable by thecaregiver both having been in the single common location. In addition tothe foregoing, other computer program product aspects are described inthe claims, drawings, and text forming a part of the present disclosure.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to a computing device and instructions. Theinstructions when executed on the computing device configure thecomputing device for obtaining an indication of a first deviceassociated with and wearable by a patient hospitalized for a particularcondition; obtaining an indication of a second device associated withand wearable by a caregiver; causing a recordation of a timestamp as anautomatic response to the first device associated with and wearable bythe patient and the second device associated with and wearable by acaregiver both being in a single common location; and describes causinga retrieval of the timestamp in response to an indication of aninstitutional readmission after the recordation of the timestampindicating the first device associated with and wearable by the patientand the second device associated with and wearable by the caregiver bothhaving been in the single common location. In addition to the foregoing,other system aspects are described in the claims, drawings, and textforming a part of the present disclosure.

An embodiment provides a method. In one implementation, the methodincludes but is not limited to obtaining an association between dataindicating a current health status of a first individual and a recorddesignator and causing a wearable article at a first care facility toinclude the data indicating the current health status of the firstindividual as an automatic and conditional response to local input atthe first care facility matching the record designator. In addition tothe foregoing, other method aspects are described in the claims,drawings, and text forming a part of the present disclosure.

In one or more various aspects, related machines, compositions ofmatter, or manufactures of systems may include virtually any combinationpermissible under 35 U.S.C. § 101 of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for obtaining an associationbetween data indicating a current health status of a first individualand a record designator and circuitry for causing a wearable article ata first care facility to include the data indicating the current healthstatus of the first individual as an automatic and conditional responseto local input at the first care facility matching the recorddesignator. In addition to the foregoing, other system aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

An embodiment provides an article of manufacture including a computerprogram product. In one implementation, the article of manufactureincludes but is not limited to a signal-bearing medium configured by oneor more instructions related to obtaining an association between dataindicating a current health status of a first individual and a recorddesignator and causing a wearable article at a first care facility toinclude the data indicating the current health status of the firstindividual as an automatic and conditional response to local input atthe first care facility matching the record designator. In addition tothe foregoing, other computer program product aspects are described inthe claims, drawings, and text forming a part of the present disclosure.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to a computing device and instructions. Theinstructions when executed on the computing device configure thecomputing device for obtaining an association between data indicating acurrent health status of a first individual and a record designator andcausing a wearable article at a first care facility to include the dataindicating the current health status of the first individual as anautomatic and conditional response to local input at the first carefacility matching the record designator. In addition to the foregoing,other system aspects are described in the claims, drawings, and textforming a part of the present disclosure.

An embodiment provides a method. In one implementation, the methodincludes but is not limited to obtaining an indication via a firstdevice local to a first individual that the first individual isnoncompliant with a first health regimen; obtaining an indication via asecond device that a second individual is available to participate in anelectronic intercommunication; and signaling the electronicintercommunication as an automatic and conditional response to theindication via the first device local to the first individual that thefirst individual is noncompliant with the first health regimen and tothe indication via the second device that the second individual isavailable to participate in the electronic intercommunication. Inaddition to the foregoing, other method aspects are described in theclaims, drawings, and text forming a part of the present disclosure.

In one or more various aspects, related machines, compositions ofmatter, or manufactures of systems may include virtually any combinationpermissible under 35 U.S.C. § 101 of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for obtaining an indication viaa first device local to a first individual that the first individual isnoncompliant with a first health regimen; circuitry for obtaining anindication via a second device that a second individual is available toparticipate in an electronic intercommunication; and circuitry forsignaling the electronic intercommunication as an automatic andconditional response to the indication via the first device local to thefirst individual that the first individual is noncompliant with thefirst health regimen and to the indication via the second device thatthe second individual is available to participate in the electronicintercommunication. In addition to the foregoing, other system aspectsare described in the claims, drawings, and text forming a part of thepresent disclosure.

An embodiment provides an article of manufacture including a computerprogram product. In one implementation, the article of manufactureincludes but is not limited to a signal-bearing medium configured by oneor more instructions related to obtaining an indication via a firstdevice local to a first individual that the first individual isnoncompliant with a first health regimen; obtaining an indication via asecond device that a second individual is available to participate in anelectronic intercommunication; and signaling the electronicintercommunication as an automatic and conditional response to theindication via the first device local to the first individual that thefirst individual is noncompliant with the first health regimen and tothe indication via the second device that the second individual isavailable to participate in the electronic intercommunication. Inaddition to the foregoing, other computer program product aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to a computing device and instructions. Theinstructions when executed on the computing device configure thecomputing device for obtaining an indication via a first device local toa first individual that the first individual is noncompliant with afirst health regimen; obtaining an indication via a second device that asecond individual is available to participate in an electronicintercommunication; and signaling the electronic intercommunication asan automatic and conditional response to the indication via the firstdevice local to the first individual that the first individual isnoncompliant with the first health regimen and to the indication via thesecond device that the second individual is available to participate inthe electronic intercommunication. In addition to the foregoing, othersystem aspects are described in the claims, drawings, and text forming apart of the present disclosure.

An embodiment provides a method. In one implementation, the methodincludes but is not limited to obtaining via a first device a scalarindication of how well a first health regimen has been followed by afirst individual; obtaining via a second device a scalar indication ofhow well a second health regimen has been followed by a secondindividual; and characterizing a performance of a third individual witha scalar evaluation obtained by mathematically combining the scalarindication of how well the first health regimen has been followed by thefirst individual with the scalar indication of how well the secondhealth regimen has been followed by the second individual. In additionto the foregoing, other method aspects are described in the claims,drawings, and text forming a part of the present disclosure.

In one or more various aspects, related machines, compositions ofmatter, or manufactures of systems may include virtually any combinationpermissible under 35 U.S.C. § 101 of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for obtaining via a firstdevice a scalar indication of how well a first health regimen has beenfollowed by a first individual; circuitry for obtaining via a seconddevice a scalar indication of how well a second health regimen has beenfollowed by a second individual; and circuitry for characterizing aperformance of a third individual with a scalar evaluation obtained bymathematically combining the scalar indication of how well the firsthealth regimen has been followed by the first individual with the scalarindication of how well the second health regimen has been followed bythe second individual. In addition to the foregoing, other systemaspects are described in the claims, drawings, and text forming a partof the present disclosure.

An embodiment provides an article of manufacture including a computerprogram product. In one implementation, the article of manufactureincludes but is not limited to a signal-bearing medium configured by oneor more instructions related to obtaining via a first device a scalarindication of how well a first health regimen has been followed by afirst individual; obtaining via a second device a scalar indication ofhow well a second health regimen has been followed by a secondindividual; and characterizing a performance of a third individual witha scalar evaluation obtained by mathematically combining the scalarindication of how well the first health regimen has been followed by thefirst individual with the scalar indication of how well the secondhealth regimen has been followed by the second individual. In additionto the foregoing, other computer program product aspects are describedin the claims, drawings, and text forming a part of the presentdisclosure.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to a computing device and instructions. Theinstructions when executed on the computing device configure thecomputing device for obtaining via a first device a scalar indication ofhow well a first health regimen has been followed by a first individual;obtaining via a second device a scalar indication of how well a secondhealth regimen has been followed by a second individual; andcharacterizing a performance of a third individual with a scalarevaluation obtained by mathematically combining the scalar indication ofhow well the first health regimen has been followed by the firstindividual with the scalar indication of how well the second healthregimen has been followed by the second individual. In addition to theforegoing, other system aspects are described in the claims, drawings,and text forming a part of the present disclosure.

An embodiment provides a method. In one implementation, the methodincludes but is not limited to obtaining a field of view within which aspecific portion of the field of view includes a view of a firstpatient; obtaining user input selectively indicating the first patientby identifying the specific portion that depicts the first patient; andsignaling medical data about the first patient as an automatic andconditional response to the user input selectively indicating the firstpatient by identifying the specific portion that depicts the firstpatient. In addition to the foregoing, other method aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

In one or more various aspects, related machines, compositions ofmatter, or manufactures of systems may include virtually any combinationpermissible under 35 U.S.C. § 101 of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for obtaining a field of viewwithin which a specific portion of the field of view includes a view ofa first patient; circuitry for obtaining user input selectivelyindicating the first patient by identifying the specific portion thatdepicts the first patient; and circuitry for signaling medical dataabout the first patient as an automatic and conditional response to theuser input selectively indicating the first patient by identifying thespecific portion that depicts the first patient. In addition to theforegoing, other system aspects are described in the claims, drawings,and text forming a part of the present disclosure.

An embodiment provides an article of manufacture including a computerprogram product. In one implementation, the article of manufactureincludes but is not limited to a signal-bearing medium configured by oneor more instructions related to obtaining a field of view within which aspecific portion of the field of view includes a view of a firstpatient; obtaining user input selectively indicating the first patientby identifying the specific portion that depicts the first patient; andsignaling medical data about the first patient as an automatic andconditional response to the user input selectively indicating the firstpatient by identifying the specific portion that depicts the firstpatient. In addition to the foregoing, other computer program productaspects are described in the claims, drawings, and text forming a partof the present disclosure.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to a computing device and instructions. Theinstructions when executed on the computing device configure thecomputing device for obtaining a field of view within which a specificportion of the field of view includes a view of a first patient;obtaining user input selectively indicating the first patient byidentifying the specific portion that depicts the first patient; andsignaling medical data about the first patient as an automatic andconditional response to the user input selectively indicating the firstpatient by identifying the specific portion that depicts the firstpatient. In addition to the foregoing, other system aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

An embodiment provides a method. In one implementation, the methodincludes but is not limited to obtaining an indication whether or not afirst individual is compliant with a first health regimen; responding tothe indication whether or not the first individual is compliant with thefirst health regimen by causing a device associated with the firstindividual to receive an indication of an artificial incentive; andsignaling a decision whether or not to manifest the artificial incentiveafter the device associated with the first individual receives theindication of the artificial incentive and responsive to an indicationwhether or not a dialog occurs between the first individual and a secondindividual. In addition to the foregoing, other method aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

In one or more various aspects, related machines, compositions ofmatter, or manufactures of systems may include virtually any combinationpermissible under 35 U.S.C. § 101 of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for obtaining an indicationwhether or not a first individual is compliant with a first healthregimen; circuitry for responding to the indication whether or not thefirst individual is compliant with the first health regimen by causing adevice associated with the first individual to receive an indication ofan artificial incentive; and circuitry for signaling a decision whetheror not to manifest the artificial incentive after the device associatedwith the first individual receives the indication of the artificialincentive and responsive to an indication whether or not a dialog occursbetween the first individual and a second individual. In addition to theforegoing, other system aspects are described in the claims, drawings,and text forming a part of the present disclosure.

An embodiment provides an article of manufacture including a computerprogram product. In one implementation, the article of manufactureincludes but is not limited to a signal-bearing medium configured by oneor more instructions related to obtaining an indication whether or not afirst individual is compliant with a first health regimen; responding tothe indication whether or not the first individual is compliant with thefirst health regimen by causing a device associated with the firstindividual to receive an indication of an artificial incentive; andsignaling a decision whether or not to manifest the artificial incentiveafter the device associated with the first individual receives theindication of the artificial incentive and responsive to an indicationwhether or not a dialog occurs between the first individual and a secondindividual. In addition to the foregoing, other computer program productaspects are described in the claims, drawings, and text forming a partof the present disclosure.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to a computing device and instructions. Theinstructions when executed on the computing device configure thecomputing device for obtaining an indication whether or not a firstindividual is compliant with a first health regimen; responding to theindication whether or not the first individual is compliant with thefirst health regimen by causing a device associated with the firstindividual to receive an indication of an artificial incentive; andsignaling a decision whether or not to manifest the artificial incentiveafter the device associated with the first individual receives theindication of the artificial incentive and responsive to an indicationwhether or not a dialog occurs between the first individual and a secondindividual. In addition to the foregoing, other system aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

An embodiment provides a method. In one implementation, the methodincludes but is not limited to obtaining a first indication whether ornot a first patient has violated a first health regimen; obtaining asecond indication whether or not the first patient has violated thefirst health regimen; signaling a decision whether or not to initiate anelectronic communication between the first patient and a provider as anautomatic and conditional response to the first indication whether ornot the first patient has violated the first health regimen but not tothe second indication whether or not the first patient has violated thefirst health regimen; and signaling a decision whether or not to routethe provider to the first patient as a conditional response to the firstindication whether or not the first patient has violated the firsthealth regimen and to the second indication whether or not the firstpatient has violated the first health regimen. In addition to theforegoing, other method aspects are described in the claims, drawings,and text forming a part of the present disclosure.

In one or more various aspects, related machines, compositions ofmatter, or manufactures of systems may include virtually any combinationpermissible under 35 U.S.C. § 101 of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for obtaining a firstindication whether or not a first patient has violated a first healthregimen; circuitry for obtaining a second indication whether or not thefirst patient has violated the first health regimen; circuitry forsignaling a decision whether or not to initiate an electroniccommunication between the first patient and a provider as an automaticand conditional response to the first indication whether or not thefirst patient has violated the first health regimen but not to thesecond indication whether or not the first patient has violated thefirst health regimen; and circuitry for signaling a decision whether ornot to route the provider to the first patient as a conditional responseto the first indication whether or not the first patient has violatedthe first health regimen and to the second indication whether or not thefirst patient has violated the first health regimen. In addition to theforegoing, other system aspects are described in the claims, drawings,and text forming a part of the present disclosure.

An embodiment provides an article of manufacture including a computerprogram product. In one implementation, the article of manufactureincludes but is not limited to a signal-bearing medium configured by oneor more instructions related to obtaining a first indication whether ornot a first patient has violated a first health regimen; obtaining asecond indication whether or not the first patient has violated thefirst health regimen; signaling a decision whether or not to initiate anelectronic communication between the first patient and a provider as anautomatic and conditional response to the first indication whether ornot the first patient has violated the first health regimen but not tothe second indication whether or not the first patient has violated thefirst health regimen; and signaling a decision whether or not to routethe provider to the first patient as a conditional response to the firstindication whether or not the first patient has violated the firsthealth regimen and to the second indication whether or not the firstpatient has violated the first health regimen. In addition to theforegoing, other computer program product aspects are described in theclaims, drawings, and text forming a part of the present disclosure.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to a computing device and instructions. Theinstructions when executed on the computing device configure thecomputing device for obtaining a first indication whether or not a firstpatient has violated a first health regimen; obtaining a secondindication whether or not the first patient has violated the firsthealth regimen; signaling a decision whether or not to initiate anelectronic communication between the first patient and a provider as anautomatic and conditional response to the first indication whether ornot the first patient has violated the first health regimen but not tothe second indication whether or not the first patient has violated thefirst health regimen; and signaling a decision whether or not to routethe provider to the first patient as a conditional response to the firstindication whether or not the first patient has violated the firsthealth regimen and to the second indication whether or not the firstpatient has violated the first health regimen. In addition to theforegoing, other system aspects are described in the claims, drawings,and text forming a part of the present disclosure.

An embodiment provides a method. In one implementation, the methodincludes but is not limited to assigning a component of an artificialincentive to a first patient partly based on an indication that thefirst patient has been admitted to a first institution in relation to aparticular condition and partly based on an indication that the firstpatient has not undergone an institutional readmission and transmittingto the first patient a result of assigning the component of theartificial incentive to the first patient partly based on the indicationthat the first patient has been admitted to the first institution inrelation to the particular condition and partly based on the indicationthat the first patient has not undergone the institutional readmission.In addition to the foregoing, other method aspects are described in theclaims, drawings, and text forming a part of the present disclosure.

In one or more various aspects, related machines, compositions ofmatter, or manufactures of systems may include virtually any combinationpermissible under 35 U.S.C. § 101 of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for assigning a component of anartificial incentive to a first patient partly based on an indicationthat the first patient has been admitted to a first institution inrelation to a particular condition and partly based on an indicationthat the first patient has not undergone an institutional readmissionand circuitry for transmitting to the first patient a result ofassigning the component of the artificial incentive to the first patientpartly based on the indication that the first patient has been admittedto the first institution in relation to the particular condition andpartly based on the indication that the first patient has not undergonethe institutional readmission. In addition to the foregoing, othersystem aspects are described in the claims, drawings, and text forming apart of the present disclosure.

An embodiment provides an article of manufacture including a computerprogram product. In one implementation, the article of manufactureincludes but is not limited to a signal-bearing medium configured by oneor more instructions related to assigning a component of an artificialincentive to a first patient partly based on an indication that thefirst patient has been admitted to a first institution in relation to aparticular condition and partly based on an indication that the firstpatient has not undergone an institutional readmission and transmittingto the first patient a result of assigning the component of theartificial incentive to the first patient partly based on the indicationthat the first patient has been admitted to the first institution inrelation to the particular condition and partly based on the indicationthat the first patient has not undergone the institutional readmission.In addition to the foregoing, other computer program product aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to a computing device and instructions. Theinstructions when executed on the computing device configure thecomputing device for assigning a component of an artificial incentive toa first patient partly based on an indication that the first patient hasbeen admitted to a first institution in relation to a particularcondition and partly based on an indication that the first patient hasnot undergone an institutional readmission and transmitting to the firstpatient a result of assigning the component of the artificial incentiveto the first patient partly based on the indication that the firstpatient has been admitted to the first institution in relation to theparticular condition and partly based on the indication that the firstpatient has not undergone the institutional readmission. In addition tothe foregoing, other system aspects are described in the claims,drawings, and text forming a part of the present disclosure.

An embodiment provides a method. In one implementation, the methodincludes but is not limited to obtaining an indication that an orderassociates a first patient with a medical device; obtaining anindication that the medical device is in a vicinity of the firstpatient; and enabling the medical device conditionally, partly based onthe indication that the order associates the first patient with themedical device and partly based on the indication that the medicaldevice is in the vicinity of the first patient. In addition to theforegoing, other method aspects are described in the claims, drawings,and text forming a part of the present disclosure.

In one or more various aspects, related machines, compositions ofmatter, or manufactures of systems may include virtually any combinationpermissible under 35 U.S.C. § 101 of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for obtaining an indicationthat an order associates a first patient with a medical device;circuitry for obtaining an indication that the medical device is in avicinity of the first patient; and circuitry for enabling the medicaldevice conditionally, partly based on the indication that the orderassociates the first patient with the medical device and partly based onthe indication that the medical device is in the vicinity of the firstpatient. In addition to the foregoing, other system aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

An embodiment provides an article of manufacture including a computerprogram product. In one implementation, the article of manufactureincludes but is not limited to a signal-bearing medium configured by oneor more instructions related to obtaining an indication that an orderassociates a first patient with a medical device; obtaining anindication that the medical device is in a vicinity of the firstpatient; and enabling the medical device conditionally, partly based onthe indication that the order associates the first patient with themedical device and partly based on the indication that the medicaldevice is in the vicinity of the first patient. In addition to theforegoing, other computer program product aspects are described in theclaims, drawings, and text forming a part of the present disclosure.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to a computing device and instructions. Theinstructions when executed on the computing device configure thecomputing device for obtaining an indication that an order associates afirst patient with a medical device; obtaining an indication that themedical device is in a vicinity of the first patient; and enabling themedical device conditionally, partly based on the indication that theorder associates the first patient with the medical device and partlybased on the indication that the medical device is in the vicinity ofthe first patient. In addition to the foregoing, other system aspectsare described in the claims, drawings, and text forming a part of thepresent disclosure.

An embodiment provides a method. In one implementation, the methodincludes but is not limited to causing a first individual to receive aplayable prompt that was automatically selected according to a firstdata component received from the first individual; receiving a seconddata component from the first individual after the first individualreceived the playable prompt that was automatically selected accordingto the first data component received from the first individual; andcausing a wearable article at a first care facility to indicate thesecond data component received from the first individual after the firstindividual received the playable prompt that was automatically selectedaccording to the first data component received from the firstindividual. In addition to the foregoing, other method aspects aredescribed in the claims, drawings, and text forming a part of thepresent disclosure.

In one or more various aspects, related machines, compositions ofmatter, or manufactures of systems may include virtually any combinationpermissible under 35 U.S.C. § 101 of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for causing a first individualto receive a playable prompt that was automatically selected accordingto a first data component received from the first individual; circuitryfor receiving a second data component from the first individual afterthe first individual received the playable prompt that was automaticallyselected according to the first data component received from the firstindividual; and circuitry for causing a wearable article at a first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual. In addition to the foregoing, othersystem aspects are described in the claims, drawings, and text forming apart of the present disclosure.

An embodiment provides an article of manufacture including a computerprogram product. In one implementation, the article of manufactureincludes but is not limited to a signal-bearing medium configured by oneor more instructions related to causing a first individual to receive aplayable prompt that was automatically selected according to a firstdata component received from the first individual; receiving a seconddata component from the first individual after the first individualreceived the playable prompt that was automatically selected accordingto the first data component received from the first individual; andcausing a wearable article at a first care facility to indicate thesecond data component received from the first individual after the firstindividual received the playable prompt that was automatically selectedaccording to the first data component received from the firstindividual. In addition to the foregoing, other computer program productaspects are described in the claims, drawings, and text forming a partof the present disclosure.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to a computing device and instructions. Theinstructions when executed on the computing device configure thecomputing device for causing a first individual to receive a playableprompt that was automatically selected according to a first datacomponent received from the first individual; receiving a second datacomponent from the first individual after the first individual receivedthe playable prompt that was automatically selected according to thefirst data component received from the first individual; and causing awearable article at a first care facility to indicate the second datacomponent received from the first individual after the first individualreceived the playable prompt that was automatically selected accordingto the first data component received from the first individual. Inaddition to the foregoing, other system aspects are described in theclaims, drawings, and text forming a part of the present disclosure.

An embodiment provides a method. In one implementation, the methodincludes but is not limited to identifying a first health regimenassociated with a first individual, the first health regimen includingone or more healthcare-related tasks associated with a time interval;causing a countdown timer to indicate a remaining portion of the timeinterval associated with the one or more healthcare-related tasksvisibly in a vicinity of the first individual; and signaling a Booleanindication of whether or not any of the one or more healthcare-relatedtasks associated with the time interval were performed within the timeinterval after the countdown timer has indicated the remaining portionof the time interval associated with the one or more healthcare-relatedtasks visibly in the vicinity of the first individual. In addition tothe foregoing, other method aspects are described in the claims,drawings, and text forming a part of the present disclosure.

In one or more various aspects, related machines, compositions ofmatter, or manufactures of systems may include virtually any combinationpermissible under 35 U.S.C. § 101 of hardware, software, and/or firmwareconfigured to effect the herein-referenced method aspects depending uponthe design choices of the system designer.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to circuitry for identifying a first healthregimen associated with a first individual, the first health regimenincluding one or more healthcare-related tasks associated with a timeinterval; circuitry for causing a countdown timer to indicate aremaining portion of the time interval associated with the one or morehealthcare-related tasks visibly in a vicinity of the first individual;and circuitry for signaling a Boolean indication of whether or not anyof the one or more healthcare-related tasks associated with the timeinterval were performed within the time interval after the countdowntimer has indicated the remaining portion of the time intervalassociated with the one or more healthcare-related tasks visibly in thevicinity of the first individual. In addition to the foregoing, othersystem aspects are described in the claims, drawings, and text forming apart of the present disclosure.

An embodiment provides an article of manufacture including a computerprogram product. In one implementation, the article of manufactureincludes but is not limited to a signal-bearing medium configured by oneor more instructions related to identifying a first health regimenassociated with a first individual, the first health regimen includingone or more healthcare-related tasks associated with a time interval;causing a countdown timer to indicate a remaining portion of the timeinterval associated with the one or more healthcare-related tasksvisibly in a vicinity of the first individual; and signaling a Booleanindication of whether or not any of the one or more healthcare-relatedtasks associated with the time interval were performed within the timeinterval after the countdown timer has indicated the remaining portionof the time interval associated with the one or more healthcare-relatedtasks visibly in the vicinity of the first individual. In addition tothe foregoing, other computer program product aspects are described inthe claims, drawings, and text forming a part of the present disclosure.

An embodiment provides a system. In one implementation, the systemincludes but is not limited to a computing device and instructions. Theinstructions when executed on the computing device configure thecomputing device for identifying a first health regimen associated witha first individual, the first health regimen including one or morehealthcare-related tasks associated with a time interval; causing acountdown timer to indicate a remaining portion of the time intervalassociated with the one or more healthcare-related tasks visibly in avicinity of the first individual; and signaling a Boolean indication ofwhether or not any of the one or more healthcare-related tasksassociated with the time interval were performed within the timeinterval after the countdown timer has indicated the remaining portionof the time interval associated with the one or more healthcare-relatedtasks visibly in the vicinity of the first individual. In addition tothe foregoing, other system aspects are described in the claims,drawings, and text forming a part of the present disclosure.

In addition to the foregoing, various other method and/or system and/orprogram product aspects are set forth and described in the teachingssuch as text (e.g., claims and/or detailed description) and/or drawingsof the present disclosure. The foregoing is a summary and thus maycontain simplifications, generalizations, inclusions, and/or omissionsof detail; consequently, those skilled in the art will appreciate thatthe summary is illustrative only and is NOT intended to be in any waylimiting. Other aspects, features, and advantages of the devices and/orprocesses and/or other subject matter described herein will becomeapparent in the teachings set forth below.

BRIEF DESCRIPTION OF THE FIGURES

For a more complete understanding of embodiments, reference now is madeto the following descriptions taken in connection with the accompanyingdrawings. The use of the same symbols in different drawings typicallyindicates similar or identical items, unless context dictates otherwise.The illustrative embodiments described in the detailed description,drawings, and claims are not meant to be limiting. Other embodiments maybe utilized, and other changes may be made, without departing from thespirit or scope of the subject matter presented here.

FIG. 1 depicts an exemplary environment in which one or moretechnologies may be implemented in one or more data-handling media.

FIG. 2 depicts an exemplary environment in which one or moretechnologies may facilitate coordination between a hospital and one ormore other facilities.

FIG. 3 depicts an exemplary environment in which one or moretechnologies may be implemented in a device.

FIGS. 4-7 respectively depict other exemplary environments in which oneor more technologies may be implemented in one or more data-handlingmedia.

FIGS. 8-13 respectively depict exemplary environments in which one ormore technologies may be configured to operate between or amongrespective devices.

FIG. 14 depicts a high-level logic flow of an operational process(described with reference to FIG. 8, e.g.).

FIG. 15 depicts a high-level logic flow of an operational process(described with reference to FIG. 9, e.g.).

FIG. 16 depicts a high-level logic flow of an operational process(described with reference to FIG. 10, e.g.).

FIG. 17 depicts a high-level logic flow of an operational process(described with reference to FIG. 11, e.g.).

FIG. 18 depicts a high-level logic flow of an operational process(described with reference to FIG. 12, e.g.).

FIG. 19 depicts a high-level logic flow of an operational process(described with reference to FIG. 13, e.g.).

FIG. 20 depicts another exemplary environment in which one or moretechnologies may be configured to operate between or among respectivedevices.

FIGS. 21-26 each depict an exemplary environment in which one or moretechnologies may be implemented in one or more data-handling media.

FIG. 27 depicts another exemplary environment in which one or moretechnologies may be implemented via one or more networked devices.

FIG. 28 depicts another exemplary environment in which one or moretechnologies may be configured to operate between or among respectivedevices.

FIG. 29 depicts another exemplary environment in which localevent-sequencing logic is configured to observe or interact with auniquely identifiable article.

FIG. 30 depicts another exemplary environment in which localevent-sequencing logic is configured to receive a signal from a sampletester or other networked device.

FIG. 31 depicts another exemplary environment in which localevent-sequencing logic is configured to receive a signal from a networkon which several records reside.

FIG. 32 depicts another exemplary environment in which localevent-sequencing logic is configured to communicate to or from adispenser or other networked device.

FIG. 33 depicts another exemplary environment in which medical deviceconfiguration logic is configured to control a disablement feature orother component of a medical device.

FIG. 34 depicts another exemplary environment in which one or moretechnologies may be configured to operate a primary unit (one or morechips, e.g.) having one or more electrical nodes.

FIG. 35 depicts another exemplary environment in which one or moretechnologies may be configured to communicate with or via a satellite.

FIG. 36 depicts another exemplary environment in which one or moretechnologies may be configured to actuate, disable, or otherwise controla disposable item.

FIG. 37 depicts another exemplary environment in which one or moretechnologies may be configured to implement a data-handling device (in ahandheld unit, e.g.).

FIG. 38 depicts another exemplary environment in which one or moretechnologies may be configured to implement a data-handling device (in awearable article, e.g.).

FIG. 48 depicts a high-level logic flow of an operational process(described with reference to FIG. 38, e.g.).

FIG. 39 depicts another exemplary environment in which one or moretechnologies may be configured to implement a local device via which acall center may communicate with a patient, e.g.).

FIG. 49 depicts a high-level logic flow of an operational process(described with reference to FIG. 39, e.g.).

FIG. 40 depicts another exemplary environment in which one or moretechnologies may be configured to implement a tracking unit useful formonitoring compliance with a health regimen.

FIG. 50 depicts a high-level logic flow of an operational process(described with reference to FIG. 40, e.g.).

FIG. 41 depicts another exemplary environment in which one or moretechnologies may be configured to implement a device (a handheld havinga touchscreen, e.g.) by which a user may designate an individual(patient, e.g.).

FIG. 51 depicts a high-level logic flow of an operational process(described with reference to FIG. 41, e.g.).

FIG. 42 depicts another exemplary environment in which one or moretechnologies may be configured to notify an individual (patient, e.g.)of a remaining portion of a time interval (associated with a task, e.g.)or of an artificial incentive (for participating in the task, e.g.).

FIG. 52 depicts a high-level logic flow of an operational process(described with reference to FIG. 42, e.g.).

FIG. 43 depicts another exemplary environment in which one or moretechnologies may be configured to implement a tiered response to ahealth regimen that is not followed.

FIG. 53 depicts a high-level logic flow of an operational process(described with reference to FIG. 43, e.g.).

FIG. 44 depicts another exemplary environment in which one or moretechnologies may be configured to implement an artificial incentive(dispensed item, e.g.) to an individual (patient released from ahospital, e.g.).

FIG. 54 depicts a high-level logic flow of an operational process(described with reference to FIG. 44, e.g.).

FIG. 45 depicts another exemplary environment in which one or moretechnologies may be configured to determine whether a medical device isin a vicinity of a patient.

FIG. 55 depicts a high-level logic flow of an operational process(described with reference to FIG. 45, e.g.).

FIG. 46 depicts another exemplary environment in which one or moretechnologies may be configured to operate a dispenser at a patient carefacility.

FIG. 56 depicts a high-level logic flow of an operational process(described with reference to FIG. 46, e.g.).

FIG. 47 depicts another exemplary environment in which one or moretechnologies may be configured to notify someone (a patient, e.g.) of aremaining portion of a time interval (associated with a task, e.g.).

FIG. 57 depicts a high-level logic flow of an operational process(described with reference to FIG. 47, e.g.).

FIG. 58 depicts variants of earlier-presented flows (in any of FIG.14-19 or 48-57).

FIG. 59 likewise depicts variants of earlier-presented flows (in any ofFIG. 14-19 or 48-58).

FIG. 60 likewise depicts variants of earlier-presented flows (in any ofFIG. 14-19 or 48-59).

FIG. 61 likewise depicts variants of earlier-presented flows (in any ofFIG. 14-19 or 48-60).

FIG. 62 likewise depicts variants of earlier-presented flows (in any ofFIG. 14-19 or 48-61).

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part hereof. In the drawings,similar symbols typically identify similar or identical components oritems, unless context dictates otherwise. The illustrative embodimentsdescribed in the detailed description, drawings, and claims are notmeant to be limiting. Other embodiments may be utilized, and otherchanges may be made, without departing from the spirit or scope of thesubject matter presented here.

The present application uses formal outline headings for clarity ofpresentation. However, it is to be understood that the outline headingsare for presentation purposes, and that different types of subjectmatter may be discussed throughout the application (e.g.,device(s)/structure(s) may be described under process(es)/operationsheading(s) and/or process(es)/operations may be discussed understructure(s)/process(es) headings; and/or descriptions of single topicsmay span two or more topic headings). Hence, the use of the formaloutline headings is not intended to be in any way limiting.

Throughout this application, examples and lists are given, withparentheses, the abbreviation “e.g.,” or both. Unless explicitlyotherwise stated, these examples and lists are merely exemplary and arenon-exhaustive. In most cases, it would be prohibitive to list everyexample and every combination. Thus, smaller, illustrative lists andexamples are used, with focus on imparting understanding of the claimterms rather than limiting the scope of such terms.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations are not expressly set forth herein for sakeof clarity.

One skilled in the art will recognize that the herein describedcomponents (e.g., operations), devices, objects, and the discussionaccompanying them are used as examples for the sake of conceptualclarity and that various configuration modifications are contemplated.Consequently, as used herein, the specific exemplars set forth and theaccompanying discussion are intended to be representative of their moregeneral classes. In general, use of any specific exemplar is intended tobe representative of its class, and the non-inclusion of specificcomponents (e.g., operations), devices, and objects should not be takenlimiting.

Those having skill in the art will recognize that the state of the arthas progressed to the point where there is little distinction leftbetween hardware, software, and/or firmware implementations of aspectsof systems; the use of hardware, software, and/or firmware is generally(but not always, in that in certain contexts the choice between hardwareand software can become significant) a design choice representing costvs. efficiency tradeoffs. Those having skill in the art will appreciatethat there are various vehicles by which processes and/or systems and/orother technologies described herein can be effected (e.g., hardware,software, and/or firmware), and that the preferred vehicle will varywith the context in which the processes and/or systems and/or othertechnologies are deployed. For example, if an implementer determinesthat speed and accuracy are paramount, the implementer may opt for amainly hardware and/or firmware vehicle; alternatively, if flexibilityis paramount, the implementer may opt for a mainly softwareimplementation; or, yet again alternatively, the implementer may opt forsome combination of hardware, software, and/or firmware in one or moremachines, compositions of matter, and articles of manufacture, limitedto patentable subject matter under 35 USC 101. Hence, there are severalpossible vehicles by which the processes and/or devices and/or othertechnologies described herein may be effected, none of which isinherently superior to the other in that any vehicle to be utilized is achoice dependent upon the context in which the vehicle will be deployedand the specific concerns (e.g., speed, flexibility, or predictability)of the implementer, any of which may vary. Those skilled in the art willrecognize that optical aspects of implementations will typically employoptically-oriented hardware, software, and or firmware.

In some implementations described herein, logic and similarimplementations may include software or other control structures.Electronic circuitry, for example, may have one or more paths ofelectrical current constructed and arranged to implement variousfunctions as described herein. In some implementations, one or moremedia may be configured to bear a device-detectable implementation whensuch media hold or transmit device detectable instructions operable toperform as described herein. In some variants, for example,implementations may include an update or modification of existingsoftware or firmware, or of gate arrays or programmable hardware, suchas by performing a reception of or a transmission of one or moreinstructions in relation to one or more operations described herein.Alternatively or additionally, in some variants, an implementation mayinclude special-purpose hardware, software, firmware components, and/orgeneral-purpose components executing or otherwise invokingspecial-purpose components. Specifications or other implementations maybe transmitted by one or more instances of tangible transmission mediaas described herein, optionally by packet transmission or otherwise bypassing through distributed media at various times.

Alternatively or additionally, implementations may include executing aspecial-purpose instruction sequence or invoking circuitry for enabling,triggering, coordinating, requesting, or otherwise causing one or moreoccurrences of virtually any functional operations described herein. Insome variants, operational or other logical descriptions herein may beexpressed as source code and compiled or otherwise invoked as anexecutable instruction sequence. In some contexts, for example,implementations may be provided, in whole or in part, by source code,such as C++, or other code sequences. In other implementations, sourceor other code implementation, using commercially available and/ortechniques in the art, may be compiled//implemented/translated/convertedinto a high-level descriptor language (e.g., initially implementingdescribed technologies in C or C++ programming language and thereafterconverting the programming language implementation into alogic-synthesizable language implementation, a hardware descriptionlanguage implementation, a hardware design simulation implementation,and/or other such similar mode(s) of expression). For example, some orall of a logical expression (e.g., computer programming languageimplementation) may be manifested as a Verilog-type hardware description(e.g., via Hardware Description Language (HDL) and/or Very High SpeedIntegrated Circuit Hardware Descriptor Language (VHDL)) or othercircuitry model which may then be used to create a physicalimplementation having hardware (e.g., an Application Specific IntegratedCircuit). Those skilled in the art will recognize how to obtain,configure, and optimize suitable transmission or computational elements,material supplies, actuators, or other structures in light of theseteachings.

The claims, description, and drawings of this application may describeone or more of the instant technologies in operational/functionallanguage, for example as a set of operations to be performed by acomputer. Such operational/functional description in most instanceswould be understood by one skilled the art as specifically-configuredhardware (e.g., because a general purpose computer in effect becomes aspecial purpose computer once it is programmed to perform particularfunctions pursuant to instructions from program software).

Importantly, although the operational/functional descriptions describedherein are understandable by the human mind, they are not abstract ideasof the operations/functions divorced from computational implementationof those operations/functions. Rather, the operations/functionsrepresent a specification for massively complex computational machinesor other means. As discussed in detail below, the operational/functionallanguage must be read in its proper technological context, i.e., asconcrete specifications for physical implementations.

The logical operations/functions described herein are a distillation ofmachine specifications or other physical mechanisms specified by theoperations/functions such that the otherwise inscrutable machinespecifications may be comprehensible to a human reader. The distillationalso allows one of skill in the art to adapt the operational/functionaldescription of the technology across many different specific vendors'hardware configurations or platforms, without being limited to specificvendors' hardware configurations or platforms.

Some of the present technical description (e.g., detailed description,drawings, claims, etc.) may be set forth in terms of logicaloperations/functions. As described in more detail herein, these logicaloperations/functions are not representations of abstract ideas, butrather are representative of static or sequenced specifications ofvarious hardware elements. Differently stated, unless context dictatesotherwise, the logical operations/functions will be understood by thoseof skill in the art to be representative of static or sequencedspecifications of various hardware elements. This is true because toolsavailable to one of skill in the art to implement technical disclosuresset forth in operational/functional formats—tools in the form of ahigh-level programming language (e.g., C, java, visual basic), etc.), ortools in the form of Very high speed Hardware Description Language(“VHDL,” which is a language that uses text to describe logiccircuits)—are generators of static or sequenced specifications ofvarious hardware configurations. This fact is sometimes obscured by thebroad term “software,” but, as shown by the following explanation, thoseskilled in the art understand that what is termed “software” is ashorthand for a massively complex interchaining/specification ofordered-matter elements. The term “ordered-matter elements” may refer tophysical components of computation, such as assemblies of electroniclogic gates, molecular computing logic constituents, quantum computingmechanisms, etc.

For example, a high-level programming language is a programming languagewith strong abstraction, e.g., multiple levels of abstraction, from thedetails of the sequential organizations, states, inputs, outputs, etc.,of the machines that a high-level programming language actuallyspecifies. See, e.g., Wikipedia, High-level programming language,http://en.wikipedia.org/wiki/High-level_programming_language (as of Jun.5, 2012, 21:00 GMT). In order to facilitate human comprehension, in manyinstances, high-level programming languages resemble or even sharesymbols with natural languages. See, e.g., Wikipedia, Natural language,http://en.wikipedia.org/wiki/Natural_language (as of Jun. 5, 2012, 21:00GMT).

It has been argued that because high-level programming languages usestrong abstraction (e.g., that they may resemble or share symbols withnatural languages), they are therefore a “purely mental construct”(e.g., that “software”—a computer program or computer programming—issomehow an ineffable mental construct, because at a high level ofabstraction, it can be conceived and understood by a human reader). Thisargument has been used to characterize technical description in the formof functions/operations as somehow “abstract ideas.” In fact, intechnological arts (e.g., the information and communicationtechnologies) this is not true.

The fact that high-level programming languages use strong abstraction tofacilitate human understanding should not be taken as an indication thatwhat is expressed is an abstract idea. In fact, those skilled in the artunderstand that just the opposite is true. If a high-level programminglanguage is the tool used to implement a technical disclosure in theform of functions/operations, those skilled in the art will recognizethat, far from being abstract, imprecise, “fuzzy,” or “mental” in anysignificant semantic sense, such a tool is instead a nearincomprehensibly precise sequential specification of specificcomputational machines—the parts of which are built up byactivating/selecting such parts from typically more generalcomputational machines over time (e.g., clocked time). This fact issometimes obscured by the superficial similarities between high-levelprogramming languages and natural languages. These superficialsimilarities also may cause a glossing over of the fact that high-levelprogramming language implementations ultimately perform valuable work bycreating/controlling many different computational machines.

The many different computational machines that a high-level programminglanguage specifies are almost unimaginably complex. At base, thehardware used in the computational machines typically consists of sometype of ordered matter (e.g., traditional electronic devices (e.g.,transistors), deoxyribonucleic acid (DNA), quantum devices, mechanicalswitches, optics, fluidics, pneumatics, optical devices (e.g., opticalinterference devices), molecules, etc.) that are arranged to form logicgates. Logic gates are typically physical devices that may beelectrically, mechanically, chemically, or otherwise driven to changephysical state in order to create a physical reality of logic, such asBoolean logic.

Logic gates may be arranged to form logic circuits, which are typicallyphysical devices that may be electrically, mechanically, chemically, orotherwise driven to create a physical reality of certain logicalfunctions. Types of logic circuits include such devices as multiplexers,registers, arithmetic logic units (ALUs), computer memory, etc., eachtype of which may be combined to form yet other types of physicaldevices, such as a central processing unit (CPU)—the best known of whichis the microprocessor. A modern microprocessor will often contain morethan one hundred million logic gates in its many logic circuits (andoften more than a billion transistors). See, e.g., Wikipedia, Logicgates, http://en.wikipedia.org/wiki/Logic_gates (as of Jun. 5, 2012,21:03 GMT).

The logic circuits forming the microprocessor are arranged to provide amicroarchitecture that will carry out the instructions defined by thatmicroprocessor's defined Instruction Set Architecture. The InstructionSet Architecture is the part of the microprocessor architecture relatedto programming, including the native data types, instructions,registers, addressing modes, memory architecture, interrupt andexception handling, and external Input/Output. See, e.g., Wikipedia,Computer architecture,http://en.wikipedia.org/wiki/Computer_architecture (as of Jun. 5, 2012,21:03 GMT).

The Instruction Set Architecture includes a specification of the machinelanguage that can be used by programmers to use/control themicroprocessor. Since the machine language instructions are such thatthey may be executed directly by the microprocessor, typically theyconsist of strings of binary digits, or bits. For example, a typicalmachine language instruction might be many bits long (e.g., 32, 64, or128 bit strings are currently common). A typical machine languageinstruction might take the form “11110000101011110000111100111111” (a 32bit instruction).

It is significant here that, although the machine language instructionsare written as sequences of binary digits, in actuality those binarydigits specify physical reality. For example, if certain semiconductorsare used to make the operations of Boolean logic a physical reality, theapparently mathematical bits “1” and “0” in a machine languageinstruction actually constitute a shorthand that specifies theapplication of specific voltages to specific wires. For example, in somesemiconductor technologies, the binary number “1” (e.g., logical “1”) ina machine language instruction specifies around +5 volts applied to aspecific “wire” (e.g., metallic traces on a printed circuit board) andthe binary number “0” (e.g., logical “0”) in a machine languageinstruction specifies around −5 volts applied to a specific “wire.” Inaddition to specifying voltages of the machines' configurations, suchmachine language instructions also select out and activate specificgroupings of logic gates from the millions of logic gates of the moregeneral machine. Thus, far from abstract mathematical expressions,machine language instruction programs, even though written as a stringof zeros and ones, specify many, many constructed physical machines orphysical machine states.

Machine language is typically incomprehensible by most humans (e.g., theabove example was just ONE instruction, and some personal computersexecute more than two billion instructions every second). See, e.g.,Wikipedia, Instructions per second,http://en.wikipedia.org/wiki/Instructions_per_second (as of Jun. 5,2012, 21:04 GMT). Thus, programs written in machine language—which maybe tens of millions of machine language instructions long—areincomprehensible to most humans. In view of this, early assemblylanguages were developed that used mnemonic codes to refer to machinelanguage instructions, rather than using the machine languageinstructions' numeric values directly (e.g., for performing amultiplication operation, programmers coded the abbreviation “mult,”which represents the binary number “011000” in MIPS machine code). Whileassembly languages were initially a great aid to humans controlling themicroprocessors to perform work, in time the complexity of the work thatneeded to be done by the humans outstripped the ability of humans tocontrol the microprocessors using merely assembly languages.

At this point, it was noted that the same tasks needed to be done overand over, and the machine language necessary to do those repetitivetasks was the same. In view of this, compilers were created. A compileris a device that takes a statement that is more comprehensible to ahuman than either machine or assembly language, such as “add 2+2 andoutput the result,” and translates that human understandable statementinto a complicated, tedious, and immense machine language code (e.g.,millions of 32, 64, or 128 bit length strings). Compilers thus translatehigh-level programming language into machine language.

This compiled machine language, as described above, is then used as thetechnical specification which sequentially constructs and causes theinteroperation of many different computational machines such thatuseful, tangible, and concrete work is done. For example, as indicatedabove, such machine language—the compiled version of the higher-levellanguage—functions as a technical specification which selects outhardware logic gates, specifies voltage levels, voltage transitiontimings, etc., such that the useful work is accomplished by thehardware.

Thus, a functional/operational technical description, when viewed by oneof skill in the art, is far from an abstract idea. Rather, such afunctional/operational technical description, when understood throughthe tools available in the art such as those just described, is insteadunderstood to be a humanly understandable representation of a hardwarespecification, the complexity and specificity of which far exceeds thecomprehension of most any one human. With this in mind, those skilled inthe art will understand that any such operational/functional technicaldescriptions—in view of the disclosures herein and the knowledge ofthose skilled in the art—may be understood as operations made intophysical reality by (a) one or more interchained physical machines, (b)interchained logic gates configured to create one or more physicalmachine(s) representative of sequential/combinatorial logic(s), (c)interchained ordered matter making up logic gates (e.g., interchainedelectronic devices (e.g., transistors), DNA, quantum devices, mechanicalswitches, optics, fluidics, pneumatics, molecules, etc.) that createphysical reality of logic(s), or (d) virtually any combination of theforegoing. Indeed, any physical object which has a stable, measurable,and changeable state may be used to construct a machine based on theabove technical description. Charles Babbage, for example, constructedthe first mechanized computational apparatus out of wood, with theapparatus powered by cranking a handle.

Thus, far from being understood as an abstract idea, those skilled inthe art will recognize a functional/operational technical description asa humanly-understandable representation of one or more almostunimaginably complex and time sequenced hardware instantiations. Thefact that functional/operational technical descriptions might lendthemselves readily to high-level computing languages (or high-levelblock diagrams for that matter) that share some words, structures,phrases, etc. with natural language should not be taken as an indicationthat such functional/operational technical descriptions are abstractideas, or mere expressions of abstract ideas. In fact, as outlinedherein, in the technological arts this is simply not true. When viewedthrough the tools available to those of skill in the art, suchfunctional/operational technical descriptions are seen as specifyinghardware configurations of almost unimaginable complexity.

As outlined above, the reason for the use of functional/operationaltechnical descriptions is at least twofold. First, the use offunctional/operational technical descriptions allows near-infinitelycomplex machines and machine operations arising from interchainedhardware elements to be described in a manner that the human mind canprocess (e.g., by mimicking natural language and logical narrativeflow). Second, the use of functional/operational technical descriptionsassists the person of skill in the art in understanding the describedsubject matter by providing a description that is more or lessindependent of any specific vendor's piece(s) of hardware.

The use of functional/operational technical descriptions assists theperson of skill in the art in understanding the described subject mattersince, as is evident from the above discussion, one could easily,although not quickly, transcribe the technical descriptions set forth inthis document as trillions of ones and zeroes, billions of single linesof assembly-level machine code, millions of logic gates, thousands ofgate arrays, or any number of intermediate levels of abstractions.However, if any such low-level technical descriptions were to replacethe present technical description, a person of skill in the art couldencounter undue difficulty in implementing the disclosure, because sucha low-level technical description would likely add complexity without acorresponding benefit (e.g., by describing the subject matter utilizingthe conventions of one or more vendor-specific pieces of hardware).Thus, the use of functional/operational technical descriptions assiststhose of skill in the art by separating the technical descriptions fromthe conventions of any vendor-specific piece of hardware.

In view of the foregoing, the logical operations/functions set forth inthe present technical description are representative of static orsequenced specifications of various ordered-matter elements, in orderthat such specifications may be comprehensible to the human mind andadaptable to create many various hardware configurations. The logicaloperations/functions disclosed herein should be treated as such, andshould not be disparagingly characterized as abstract ideas merelybecause the specifications they represent are presented in a manner thatone of skill in the art can readily understand and apply in a mannerindependent of a specific vendor's hardware implementation.

Those skilled in the art will recognize that it is common within the artto implement devices and/or processes and/or systems, and thereafter useengineering and/or other practices to integrate such implemented devicesand/or processes and/or systems into more comprehensive devices and/orprocesses and/or systems. That is, at least a portion of the devicesand/or processes and/or systems described herein can be integrated intoother devices and/or processes and/or systems via a reasonable amount ofexperimentation. Those having skill in the art will recognize thatexamples of such other devices and/or processes and/or systems mightinclude—as appropriate to context and application—all or part of devicesand/or processes and/or systems of (a) an air conveyance (e.g., anairplane, rocket, helicopter, etc.), (b) a ground conveyance (e.g., acar, truck, locomotive, tank, armored personnel carrier, etc.), (c) abuilding (e.g., a home, warehouse, office, etc.), (d) an appliance(e.g., a refrigerator, a washing machine, a dryer, etc.), (e) acommunications system (e.g., a networked system, a telephone system, aVoice over IP system, etc.), (f) a business entity (e.g., an InternetService Provider (ISP) entity such as Comcast Cable, Qwest, SouthwesternBell, etc.), or (g) a wired/wireless services entity (e.g., Sprint,Cingular, Nextel, etc.), etc.

In certain cases, use of a system or method may occur in a territoryeven if components are located outside the territory. For example, in adistributed computing context, use of a distributed computing system mayoccur in a territory even though parts of the system may be locatedoutside of the territory (e.g., relay, server, processor, signal-bearingmedium, transmitting computer, receiving computer, etc. located outsidethe territory).

A sale of a system or method may likewise occur in a territory even ifcomponents of the system or method are located and/or used outside theterritory. Further, implementation of at least part of a system forperforming a method in one territory does not preclude use of the systemin another territory

One skilled in the art will recognize that the herein describedcomponents (e.g., operations), devices, objects, and the discussionaccompanying them are used as examples for the sake of conceptualclarity and that various configuration modifications are contemplated.Consequently, as used herein, the specific exemplars set forth and theaccompanying discussion are intended to be representative of their moregeneral classes. In general, use of any specific exemplar is intended tobe representative of its class, and the non-inclusion of specificcomponents (e.g., operations), devices, and objects should not be takenlimiting.

The herein described subject matter sometimes illustrates differentcomponents contained within, or connected with, different othercomponents. It is to be understood that such depicted architectures aremerely exemplary, and that in fact many other architectures may beimplemented which achieve the same functionality. In a conceptual sense,any arrangement of components to achieve the same functionality iseffectively “associated” such that the desired functionality isachieved. Hence, any two components herein combined to achieve aparticular functionality can be seen as “associated with” each othersuch that the desired functionality is achieved, irrespective ofarchitectures or intermedial components. Likewise, any two components soassociated can also be viewed as being “operably connected”, or“operably coupled,” to each other to achieve the desired functionality,and any two components capable of being so associated can also be viewedas being “operably couplable,” to each other to achieve the desiredfunctionality. Specific examples of operably couplable include but arenot limited to physically mateable and/or physically interactingcomponents, and/or wirelessly interactable, and/or wirelesslyinteracting components, and/or logically interacting, and/or logicallyinteractable components.

In some instances, one or more components may be referred to herein as“configured to,” “configured by,” “configurable to,” “operable/operativeto,” “adapted/adaptable,” “able to,” “conformable/conformed to,” etc.Those skilled in the art will recognize that such terms (e.g.“configured to”) generally encompass active-state components and/orinactive-state components and/or standby-state components, unlesscontext requires otherwise.

In a general sense, those skilled in the art will recognize that thevarious embodiments described herein can be implemented, individuallyand/or collectively, by various types of electro-mechanical systemshaving a wide range of electrical components such as hardware, software,firmware, and/or virtually any combination thereof, limited topatentable subject matter under 35 U.S.C. 101; and a wide range ofcomponents that may impart mechanical force or motion such as rigidbodies, spring or torsional bodies, hydraulics, electro-magneticallyactuated devices, and/or virtually any combination thereof.Consequently, as used herein “electro-mechanical system” includes, butis not limited to, electrical circuitry operably coupled with atransducer (e.g., an actuator, a motor, a piezoelectric crystal, a MicroElectro Mechanical System (MEMS), etc.), electrical circuitry having atleast one discrete electrical circuit, electrical circuitry having atleast one integrated circuit, electrical circuitry having at least oneapplication specific integrated circuit, electrical circuitry forming ageneral purpose computing device configured by a computer program (e.g.,a general purpose computer configured by a computer program which atleast partially carries out processes and/or devices described herein,or a microprocessor configured by a computer program which at leastpartially carries out processes and/or devices described herein),electrical circuitry forming a memory device (e.g., forms of memory(e.g., random access, flash, read only, etc.)), electrical circuitryforming a communications device (e.g., a modem, communications switch,optical-electrical equipment, etc.), and/or any non-electrical analogthereto, such as optical or other analogs (e.g., graphene basedcircuitry). Those skilled in the art will also appreciate that examplesof electro-mechanical systems include but are not limited to a varietyof consumer electronics systems, medical devices, as well as othersystems such as motorized transport systems, factory automation systems,security systems, and/or communication/computing systems. Those skilledin the art will recognize that electro-mechanical as used herein is notnecessarily limited to a system that has both electrical and mechanicalactuation except as context may dictate otherwise.

In a general sense, those skilled in the art will recognize that thevarious aspects described herein which can be implemented, individuallyand/or collectively, by a wide range of hardware, software, firmware,and/or any combination thereof can be viewed as being composed ofvarious types of “electrical circuitry.” Consequently, as used herein“electrical circuitry” includes, but is not limited to, electricalcircuitry having at least one discrete electrical circuit, electricalcircuitry having at least one integrated circuit, electrical circuitryhaving at least one application specific integrated circuit, electricalcircuitry forming a general purpose computing device configured by acomputer program (e.g., a general purpose computer configured by acomputer program which at least partially carries out processes and/ordevices described herein, or a microprocessor configured by a computerprogram which at least partially carries out processes and/or devicesdescribed herein), electrical circuitry forming a memory device (e.g.,forms of memory (e.g., random access, flash, read only, etc.)), and/orelectrical circuitry forming a communications device (e.g., a modem,communications switch, optical-electrical equipment, etc.). Those havingskill in the art will recognize that the subject matter described hereinmay be implemented in an analog or digital fashion or some combinationthereof.

Those skilled in the art will recognize that at least a portion of thedevices and/or processes described herein can be integrated into a dataprocessing system. Those having skill in the art will recognize that adata processing system generally includes one or more of a system unithousing, a video display device, memory such as volatile or non-volatilememory, processors such as microprocessors or digital signal processors,computational entities such as operating systems, drivers, graphicaluser interfaces, and applications programs, one or more interactiondevices (e.g., a touch pad, a touch screen, an antenna, etc.), and/orcontrol systems including feedback loops and control motors (e.g.,feedback for sensing position and/or velocity; control motors for movingand/or adjusting components and/or quantities). A data processing systemmay be implemented utilizing suitable commercially available components,such as those typically found in data computing/communication and/ornetwork computing/communication systems.

For the purposes of this application, “cloud” computing may beunderstood as described in the cloud computing literature. For example,cloud computing may be methods and/or systems for the delivery ofcomputational capacity and/or storage capacity as a service. The “cloud”may refer to one or more hardware and/or software components thatdeliver or assist in the delivery of computational and/or storagecapacity, including, but not limited to, one or more of a client, anapplication, a platform, an infrastructure, and/or a server The cloudmay refer to any of the hardware and/or software associated with aclient, an application, a platform, an infrastructure, and/or a server.For example, cloud and cloud computing may refer to one or more of acomputer, a processor, a storage medium, a router, a switch, a modem, avirtual machine (e.g., a virtual server), a data center, an operatingsystem, a middleware, a firmware, a hardware back-end, a softwareback-end, and/or a software application. A cloud may refer to a privatecloud, a public cloud, a hybrid cloud, and/or a community cloud. A cloudmay be a shared pool of configurable computing resources, which may bepublic, private, semi-private, distributable, scaleable, flexible,temporary, virtual, and/or physical. A cloud or cloud service may bedelivered over one or more types of network, e.g., a mobilecommunication network, and the Internet.

As used in this application, a cloud or a cloud service may include oneor more of infrastructure-as-a-service (“IaaS”), platform-as-a-service(“PaaS”), software-as-a-service (“SaaS”), and/or desktop-as-a-service(“DaaS”). As a non-exclusive example, IaaS may include, e.g., one ormore virtual server instantiations that may start, stop, access, and/orconfigure virtual servers and/or storage centers (e.g., providing one ormore processors, storage space, and/or network resources on-demand,e.g., EMC and Rackspace). PaaS may include, e.g., one or more softwareand/or development tools hosted on an infrastructure (e.g., a computingplatform and/or a solution stack from which the client can createsoftware interfaces and applications, e.g., Microsoft Azure). SaaS mayinclude, e.g., software hosted by a service provider and accessible overa network (e.g., the software for the application and/or the dataassociated with that software application may be kept on the network,e.g., Google Apps, SalesForce). DaaS may include, e.g., providingdesktop, applications, data, and/or services for the user over a network(e.g., providing a multi-application framework, the applications in theframework, the data associated with the applications, and/or servicesrelated to the applications and/or the data over the network, e.g.,Citrix). The foregoing is intended to be exemplary of the types ofsystems and/or methods referred to in this application as “cloud” or“cloud computing” and should not be considered complete or exhaustive.

The proliferation of automation in many transactions is apparent. Forexample, Automated Teller Machines (“ATMs”) dispense money and receivedeposits. Airline ticket counter machines check passengers in, dispensetickets, and allow passengers to change or upgrade flights. Train andsubway ticket counter machines allow passengers to purchase a ticket toa particular destination without invoking a human interaction at all.Many groceries and pharmacies have self-service checkout machines whichallow a consumer to pay for goods purchased by interacting only with amachine. Large companies now staff telephone answering systems withmachines that interact with customers, and invoke a human in thetransaction only if there is a problem with the machine-facilitatedtransaction.

Nevertheless, as such automation increases, convenience andaccessibility may decrease. Self-checkout machines at grocery stores maybe difficult to operate. ATMs and ticket counter machines may be mostlyinaccessible to disabled persons or persons requiring special access.Where before, the interaction with a human would allow disabled personsto complete transactions with relative ease, if a disabled person isunable to push the buttons on an ATM, there is little the machine can doto facilitate the transaction to completion. While some of these publicterminals allow speech operations, they are configured to the mostgeneric forms of speech, which may be less useful in recognizingparticular speakers, thereby leading to frustration for users attemptingto speak to the machine. This problem may be especially challenging forthe disabled, who already may face significant challenges in completingtransactions with automated machines.

In addition, smartphones and tablet devices also now are configured toreceive speech commands. Speech and voice controlled automobile systemsnow appear regularly in motor vehicles, even in economical,mass-produced vehicles. Home entertainment devices, e.g., disc players,televisions, radios, stereos, and the like, may respond to speechcommands. Additionally, home security systems may respond to speechcommands. In an office setting, a worker's computer may respond tospeech from that worker, allowing faster, more efficient work flows.Such systems and machines may be trained to operate with particularusers, either through explicit training or through repeatedinteractions. Nevertheless, when that system is upgraded or replaced,e.g., a new television is purchased, that training may be lost with thedevice. Thus, in some embodiments described herein, adaptation data forspeech recognition systems may be separated from the device whichrecognizes the speech, and may be more closely associated with a user,e.g., through a device carried by the user, or through a networklocation associated with the user.

Further, in some environments, there may be more than one device thattransmits and receives data within a range of interacting with a user.For example, merely sitting on a couch watching television may involvefive or more devices, e.g., a television, a cable box, an audio/visualreceiver, a remote control, and a smartphone device. Some of thesedevices may transmit or receive speech data. Some of these devices maytransmit, receive, or store adaptation data, as will be described inmore detail herein. Thus, in some embodiments, which will be describedin more detail herein, there may be methods, systems, and devices fordetermining which devices in a system should perform actions that allowa user to efficiently interact with an intended device through thatuser's speech.

With reference now to FIG. 1, shown is an example of a system 1 (anetwork subsystem, e.g.) in which one or more technologies may beimplemented. One or more media 105 are configured to bear one or moreinstances of a registry 109 (of multiple subscribers, e.g.); organizedinformational data components relating to health-related protocols 120,130, 140 relating to the treatment of various conditions 160, 170, 180(symptoms or pathologies 181 or sets 107 thereof, e.g.); thresholds 191,192; and outputs 195, 196. One or more such data components 126 relatespecifically to the handling of condition 160 using protocol 120prospectively or otherwise, for example, for one or more particularpatients or more generally as described below. (Such sets 107 ofpathologies 181 may comprise one or more of an addiction or chronic painor major depression, for example.) One or more data components 127likewise relate specifically to the handling of condition 170 usingprotocol 120 (MRI screening followed by magnetic stimulation therapy,e.g.). One or more data components 128 likewise relate specifically tothe handling of condition 180 using protocol 120.

One or more data components 136 likewise relate specifically to thehandling of condition 160 using protocol 130. One or more datacomponents 137 likewise relate specifically to the handling of condition170 (hypertension with major depression in a male of 50 years or older,e.g.) using protocol 130 (a series of ten weekly counseling sessions,e.g.). One or more data components 138 likewise relate specifically tothe handling of condition 180 using protocol 130.

One or more data components 146 likewise relate specifically to thehandling of condition 160 using protocol 140. One or more datacomponents 147 likewise relate specifically to the handling of condition170 (major depression, e.g.) using protocol 140. In some contexts,protocol 140 may comprise a particular drug 141 (sertraline, e.g.) takenat a particular dosage (50 milligrams, e.g.) with a particular frequency144 (daily, e.g.). One or more data components 148 likewise relatespecifically to the handling of condition 180 using protocol 140.

A wide variety of conditions 160, 170, 180 of interest may be identifiedusing one or more common medical classification publications: the ICD(International Classification of Diseases); the ICSD (InternationalClassification of Sleep Disorders); the NANDA (North American NursingDiagnosis Association); the DSM-IV (Diagnostic and Statistical Manual ofMental Disorders); the Mendelian Inheritance in Man; and the SNOMED(Systematized Nomenclature of Human Medicine, D axis). In practicalterms, records signaling such conditions may also comprise textualdescriptors to locate misclassified or other data components 126, 137,148 that signal such conditions 160, 170, 180 of interest (in aphysician's remarks or other annotations relating to patients who havebeen readmitted to a psychiatric or other care facility, e.g.).

Likewise a wide variety of protocols 120, 130, 140 (of diagnosis ortreatment, e.g.) of interest may be identified using one or more commonprocedure codes in various publications: the ICHI (InternationalClassification of Health Interventions); the ICPM (InternationalClassification of Procedures in Medicine); the ICPC-2 (InternationalClassification of Primary Care); the HCPCS (Healthcare Common ProcedureCoding System); the ICD-10-PCS and the ICD-9-CM Volume 3 (InternationalClassification of Diseases); the NIC (Nursing InterventionsClassification); the NMDS (Nursing Minimum Data Set); the NOC (NursingOutcomes Classification); the SNOMED (Systematized Nomenclature of HumanMedicine, P axis); and the CPT (Current Procedural Terminology) codes.In practical terms, records signaling such protocols may also compriseDRG (Diagnosis Related Group) codes or textual descriptors to locatemisclassified or other data components 126, 137, 148 that signal suchprotocols 120, 130, 140 of interest.

With reference now to FIG. 2, shown is an example of variousinstitutions among which one or more technologies may be implemented. Amotor vehicle bearing a mobile device 241 is shown in a vicinity of ahospital 201 on a network 290 (the Internet or a phone network, e.g.)shared with another hospital 202 and a home 289 of a patient 250. Insome contexts, network 290 may include one or more call centers 295operated by one or more agents 294 as described below. A stationarydevice 242 is configured to monitor a location 204 within which itresides (in or near an emergency room of hospital 202, e.g.). In theparticular context as shown, hospital 201 is in one service zone 207 andhospital 202 is in a second service zone 208.

With reference now to FIG. 3, shown is another example of a system 3 (asubsystem comprising network 290, e.g.) in which one or moretechnologies may be implemented. Device 305 may (optionally) include oneor more instances of input modules 311, 312, 313, 314, 315, 316, 317,318, 319; of configuration modules 321, 322, 323, 324, 325, 326; ofrequest modules 331, 332; of retrieval modules 341, 342, 343, 344; ofresponse modules 351, 352, 353, 354, 355, 356, 357, 358, 359; ofinvocation modules 371, 372, 373, 374; of statement modules 381, 382; ofcomparators 391; of clocks 392; of expert systems 393; of transmitters394; of global positioning systems 396; of radio frequencyidentification (RFID) transponders 397; or of ultrasound identification(USID) transponders 398. In some contexts, moreover, a single component(an application-specific integrated circuit or device-executablesoftware, e.g.) may implement two or more types of the modules describedbelow. Input module 319, for example, may (optionally) be configured toimplement more than one of input modules 311-318 (as an automaticresponse to device-detectable events as described below, e.g.). Responsemodule 359 may likewise be configured to implement more than one ofresponse modules 351-358 (in response to an activation signal frominvocation module 374, e.g.). In many of the contexts described below,two or more instances of device 305 are configured to interact with oneanother or to include one or more media 105 as described below. SeeFIGS. 4-7, 21, and 22.

With reference now to FIG. 4, shown is another example of a system 4 (anetwork subsystem, e.g.) in which one or more technologies may beimplemented. One or more media 405 are configured to bear one or moreinstances of content 431, 432; of protocol data 450; of patientattributes 470 (gender 471 or age 472 or race 473, e.g.); of biometrics481, test results 482, computed tomography scans 483 or other images484; or other such diagnostic data 490. Each of the data components126-128, 136-138, 146-148 that pertain to a particular patient 250, forexample, may (optionally) include one or more protocol identifiers 451,material identifiers 452 (of drugs, e.g.), timing data 453 (of dosages,e.g.), protocol effectiveness indicators 456 (such as rankings 454 orscores 455, e.g.), or dates 457 (of orders or enrollments or injuries orother major events, e.g.) as well as diagnostic data 490 relating toeach selected protocol (documenting its rationale or apparent effect,e.g.).

With reference now to FIG. 5, shown is another example of a system 5 (anetwork subsystem, e.g.) in which one or more technologies may beimplemented. One or more media 505 are configured to bear one or moreinstances of pathology identifiers 511, symptom identifiers 512,complaints 513, or other such condition indications 515; of report types521, request authorizations 522, user identifiers 523, or other suchindications 525 (of excessive institutional readmissions or otherapparently negative outcomes that warrant scrutiny, e.g.); of timeintervals 538 or programmatic delays 541, 542, 543, 544; of inputs 551,552 or replies 555; of records 561, 562, 563, 564, 565, 566, 567, 568,569 relating to a particular patient or caregiver; of queries 571, 572,573, 574 or requests 581, 582 as described below.

With reference now to FIG. 6, shown is another example of a system 6 (anetwork subsystem, e.g.) in which one or more technologies may beimplemented. One or more media 605 are configured to bear one or moreinstances of accounts 616 (relating to funds or other inventories,e.g.); orders 618 (by a physician, e.g.); components 651, 652 of aregimen 650; records 671, 672, 673, 674, 675 relating to a particularpatient or caregiver; indications 681, 682, 683, 684, 685, 686, 687,688, 689 of various events or conditions relating to healthcare orinformation management; or of goods 691, services 692, credits 693, orother incentives 694 as described below.

With reference now to FIG. 7, shown is another example of a system 7 (anetwork subsystem, e.g.) in which one or more technologies may beimplemented. One or more media 705 are configured to bear one or moreinstances of validations 701, 702; records 710 (comprising timestamps711 or other data 712 manifesting measurement or observation events,e.g.); e-mail addresses 721, telephone numbers 722, or other contactinformation 720 (of a care provider or administrator, e.g.); preferences725 (of users of devices 305 as described below, e.g.); identifiers 731,732, 733, 734, 735 (of devices or individuals, e.g.); coded or otherdigitally expressed exceptions 740 affecting treatment decisions (costdifferences 741, side effects 742, past failures 743, or patientpreferences 744, e.g.); global positioning system (GPS) data 751, 752(of devices or individuals as described below, e.g.); data 764comprising medical justification audit reports 765; indications 777comprising requests 771, 772 (signaling an association 776 between acaregiver or patient and various indications 681-689 described below,e.g.); and scans 788, 789 (of documents supporting a course oftreatment, e.g.).

Several variants described herein refer to device-detectable“implementations” such as one or more instances of computer-readablecode, transistor or latch connectivity layouts or other geometricexpressions of logical elements, firmware or software expressions oftransfer functions implementing computational specifications, digitalexpressions of truth tables, or the like. Such instances can, in someimplementations, include source code or other human-readable portions.Alternatively or additionally, functions of implementations describedherein may constitute one or more device-detectable outputs such asdecisions, manifestations, side effects, results, coding or otherexpressions, displayable images, data files, data associations,statistical correlations, streaming signals, intensity levels,frequencies or other measurable attributes, packets or other encodedexpressions, or the like from invoking or monitoring the implementationas described herein.

In some embodiments, a “state” of a component may comprise “available”or some other such state-descriptive labels, an event count or othersuch memory values, a partial depletion or other such physical propertyof a supply device, a voltage, or any other such conditions orattributes that may change between two or more possible valuesirrespective of device location. Such states may be received directly asa measurement or other detection, in some variants, and/or may beinferred from a component's behavior over time. A distributed or othercomposite system may comprise vector-valued device states, moreover,which may affect dispensations or departures in various ways asexemplified herein.

“Received,” “particular,” “wearable,” “portable,” “precedent,”“stationary,” “audible,” “conditional,” “explicit,” “prior,”“extrinsic,” “mobile,” “specific,” “partly,” “local,” “between,”“passive,” “associated,” “effective,” “single,” “wireless,” “any,”“within,” “automatic,” “proximate,” “remote,” “common,” “selective,”“explicit,” “resident,” “employed,” “detectable,” “multiple,” “in avicinity,” “visible,” “objective,” “matching,” “artificial,”“institutional,” “medical,” or other such descriptors herein are used intheir normal yes-or-no sense, not as terms of degree, unless contextdictates otherwise. “Compliant,” for example, is used in its normalyes-or-no sense except in contexts that describe degrees of compliancewith particularity (quantifying “how well” a regimen has been followed,e.g.). In light of the present disclosure those skilled in the art willunderstand from context what is meant by “vicinity,” by being “in” or“at” a detection region, by “remote,” and by other such positionaldescriptors used herein. Terms like “processor,” “center,” “unit,”“computer,” or other such descriptors herein are used in their normalsense, in reference to an inanimate structure. Such terms do not includeany people, irrespective of their location or employment or otherassociation with the thing described, unless context dictates otherwise.A “hospital” may refer merely to a facility (one or morebrick-and-mortar buildings, e.g.) adapted for administering medicalcare, for example, except in contexts that describe an abstractinstitution with particularity (relating to whether such institutionshave “admitted” a patient, e.g.). “For” is not used to articulate a mereintended purpose in phrases like “circuitry for” or “instruction for,”moreover, but is used normally, in descriptively identifying specialpurpose circuitry or code.

In some embodiments a “manual” occurrence includes, but is not limitedto, one that results from one or more actions consciously taken by adevice user in real time. Conversely an “automatic” occurrence is notaffected by any action consciously taken by a device user in real timeexcept where context dictates otherwise.

In some embodiments, “signaling” something can include identifying,contacting, requesting, selecting, or indicating the thing. In somecases a signaled thing is susceptible to fewer than all of theseaspects, of course, such as a task definition that cannot be“contacted.”

In some embodiments, “status indicative” data can reflect a trend orother time-dependent phenomenon indicating some aspect of a subject'scondition. Alternatively or additionally, a status indicative data setcan include portions that have no bearing upon such status. Althoughsome types of distillations can require authority or substantialexpertise (e.g. making a final decision upon a risky procedure or othercourse of treatment), many other types of distillations can readily beimplemented without undue experimentation in light of teachings herein.

In some embodiments, “causing” events can include triggering, producingor otherwise directly or indirectly bringing the events to pass. Thiscan include causing the events remotely, concurrently, partially, orotherwise as a “cause in fact,” whether or not a more immediate causealso exists.

Some descriptions herein refer to an “indication whether” an event hasoccurred. An indication is “positive” if it indicates that the event hasoccurred, irrespective of its numerical sign or lack thereof. Whetherpositive or negative, such indications may be weak (i.e. slightlyprobative), definitive, or many levels in between. In some cases the“indication” may include a portion that is indeterminate, such as anirrelevant portion of a useful photograph.

With reference now to FIG. 8, shown is another example of a system 8 (asubsystem of one or more networks 290, 890 described herein, e.g.) inwhich one or more technologies may be implemented. A desktop scanner 878is configured to transmit a scan 811 of a hardcopy 877 (of a medicaljournal article, e.g.) to a local system 841 (comprising a display 810and keyboard 846, e.g.) on one or more networks 290, 890 describedherein. One such network 890 comprises a records archive 820 accessibleby one or more retrieval modules 825 operable by a remote requestor 893(remote from local system 841, e.g.).

With reference now to FIG. 14, shown is a high-level logic flow 14 of anoperational process. Intensive operation 42 describes causing anelectronic record of a first protocol for a particular condition to beannotated with a scan of a document (e.g. configuration module 326amending a digital record 569 of the first protocol to include areference to or a copy of a digital scan 811 of a hard copy 877 inresponse to input module 314 receiving the reference to or the copy ofthe digital scan 811). This can occur, for example, in a context inwhich record 569 reflects patient 250 being admitted or having beenadmitted to hospital 201 for the treatment of a particular condition 170by a specific protocol 120, in which network 290 is linked to network890, in which one or more instances of device 305 reside on network 890(implementing a computer workstation comprising system 841, e.g.), inwhich one or more input modules 311-319 receive the digital scan 811 asan automatic response to scanner 878 receiving the hard copy 877, and inwhich configuration module 326 fully implements the annotation (directlyto a remote instance of record 569, e.g.) without any manual input (asan additional automatic response to scanner 878 receiving the hard copy877, e.g.). Alternatively, input module 314 may be configured to confirmthat a caregiver wants such annotation or to permit the caregiver totune the annotation (by adding related notes or orders or by annotatingother records 561-569, 3191-3197 with the same scan 811, e.g.). In somevariants, for example, the local user can confirm that the changes madeto a local instance of record 569 (including a locally indicated ordisplayed scan 811, e.g.) should be written to a remote records archive820 (into a data component 127 specifically associated with the protocol120 and with the condition 170, e.g.) by responding affirmatively to aquery 572 like “save changes to the current record?”

Extensive operation 61 describes retrieving the electronic record of thefirst protocol after the electronic record of the first protocol isannotated with the scan of the document partly based on an indication ofa first patient undergoing the first protocol and partly based on anindication of an institutional readmission (e.g. retrieval module 825retrieving record 569 based on indications that patient 250 was treatedfor the particular condition 170 at hospital 201 and was released andlater readmitted for the same condition 170). This can occur, forexample, in a context in which record 569 includes a symptom identifier512 or other indication 681 of the specific medical condition 170, inwhich record 569 also includes a color scan 811 of content 431pertaining to the medical condition 170 presented in the form of a hardcopy 877 (a research study provided by the patient 250 or a familymember, e.g.), and in which such later readmission (for the particularcondition or for a treatment of some harm to the patient resulting froma medical error that occurred during the prior hospitalization, e.g.)would otherwise trigger a reduction in payment for the “first” protocolor for other hospital services. In some contexts, for example, aMultidrug-Resistant Staphylococcus Aureus (MRSA) diagnosis that appearsduring a patient's hospital stay, or some other hospital-acquiredcondition, may be indicative of such medical error. Alternatively oradditionally, such content 431 (in one or more media 105, 405 residingon network 890, e.g.) may pertain to one or more medical protocols 120,130 under prospective consideration for treating the patient 250 and maybe retained (as evidence of diligent decision-making or of why a courseof treatment was not selected, e.g.).

With reference now to FIG. 9, shown is another example of a system 9(e.g. a subsystem of one or more networks 290, 990) in which one or moretechnologies may be implemented. A desktop system 941 is configured todisplay (to a caregiver 991 or other authorized entity, e.g.) one ormore instances of studies 931, records 932, forms 933, or other suchindications relating to a patient 992. Such records 932 may includevarious data components 127, 136, 148 relating to therapies (actually orpotentially) being performed upon one or more patients 250, 992 asdescribed herein. In some contexts, one or more such records 932 may beretrieved from or saved to records archive 920 (by one or more retrievalmodules 925 in an implementation of device 305 described above, e.g.).Alternatively or additionally, a regional network 990 (e.g. for one ormore hospitals 201, 202) containing such archives may be accessed (by aremote requestor 993, e.g.) as described herein.

With reference now to FIG. 15, shown is a high-level logic flow 15 of anoperational process. Intensive operation 35 describes obtaining anindication that a particular condition was treated in a first patientwith a first protocol (e.g. input module 316 receiving a medical record932 or other specific indication 935 that protocol 120 was used fortreating condition 170 in patient 250). This can occur, for example, ina context in which one or more such indications 935 comprise a datacomponent 127 associated with protocol 120 and with condition 170, inwhich a second patient 992 or her caregiver 991 has access to some orall of the data component 127 (including the specific indication 935,e.g.), and in which condition 170 is described in data component 127with a pathology identifier 511 (“fibromyalgia,” e.g.) that has alsobeen assigned to the “second” patient 992. In some variants, forexample, one or more such data components 126-128, 136-138 may reside inone or more regional records archives 820, 920 accessible to authorizedcaregivers 991. Alternatively or additionally, one or more suchindications 935 may be obtained from a published research study 931 (asa hard copy 877 to be scanned, e.g.) or entered into an online form 933(with an identifier of a hospital 201 or a physician or protocol data450 or other background information known to caregiver 991 about the“first” patient 250 or his/her prior treatment, e.g.).

Intensive operation 43 describes causing a record of a second patient toinclude the indication that the particular condition was treated in thefirst patient with the first protocol (e.g. configuration module 323modifying a medical record 562 of the “second” patient 992 by includingone or more specific indications 935 that protocol 120 was used fortreating condition 170 in one or more prior patients 250, with orwithout identifying any particular “first” patient 250). This can occur,for example, in a context in which protocol 120 is not yet establishedas the preferred treatment for treating condition 170; in which the“first” and “second” patients have one or more attributes 470 (gender471 or general age 472 or race 473, e.g.) in common; in which record 562identifies one or more such attributes 470 but does not include otherinformation that identifies the “first” patient 250. In addition to suchconsiderations relating to patient privacy, tracking such informationmay be helpful in relation to other regulatory considerations. Under thehealthcare system in the United States, for example, Section 4302 ofPublic Law 111-148 (the “Patient Protection and Affordable Care Act,”sometimes called “Obamacare”) “[r]equires federally conducted orsupported healthcare programs or surveys to collect and reportdemographic data, including ethnicity, sex, primary language, anddisability status, as well as data at the smallest geographic levelpossible, such as state or local, etc.”

Referring again to FIGS. 1 & 9, moreover, in some contexts a caregiver991 may determine a circumstance of the “second” patient falls into oneor more identifiable exceptions 740 to a general practice of treatingcondition 170 with a more conventional protocol 140. In a context inwhich the conventional protocol 140 is characterized by one or moregenerally preferred drugs 141 and associated dosages 142, practicegroups or facilities or modes (in-patient at hospital 201, e.g.), orfrequencies of treatment (daily or weekly, e.g.), an unconventionalprotocol 120 may be warranted for one or more reasons of cost difference741 (protocol 140 being too expensive for continued use, e.g.); sideeffects 742 (an allergy to drug 141 or drug interaction risk, e.g.);past failure 743 (having been ineffective for treating condition 170 inpatient 992, e.g.); or a documented preference 744 (manifested by awaiver from “second” patient 992, e.g.). In some variants, therefore, itmay be preferable for configuration module 323 to be operable formodifying medical record 562 to include such exceptions 740 incircumstance (optionally by querying caregiver 991 for such information,e.g.).

Extensive operation 62 describes retrieving the record of the secondpatient selectively in response to an association between the secondpatient and an indication of an institutional readmission after therecord of the second patient includes the indication that the particularcondition was treated in the first patient with the first protocol (e.g.retrieval module 925 requesting and providing medical record 562 inresponse to a remote requestor 993 initiating a medical justificationaudit report 765 indicating that the “second” patient 992 underwentmultiple in-patient treatments for condition 170 during separatehospital stays). This can occur, for example, in a context in whichoperations 35 and 43 had both been performed; in which the retrieval is“selective” insofar that each instance of operation 62 retrieves lessthan all such records 561-569, 3191-3197 (of billing, e.g.); in whichcaregiver 991 has reasonably and correctly relied upon the indication935 as precedent (that the particular condition 170 was treated in the“first” patient 250 with protocol 120, e.g.) in her decision torecommend or administer protocol 120 to the “second” patient 992 inhospital 201; in which it is not self-evident that such administrationwas reasonable in the absence of the specific indication 935; and inwhich protocol 120 is ultimately not permanently effective ateradicating the particular condition 170. In the event that the “second”patient 992 is readmitted to hospital 202 later for further treatment ofthe particular condition 170 and that such readmission would otherwisetrigger a reduction in payment for the services of caregiver 991 or ofhospital 201, remembering and reacquiring the particular condition 170(or some other adequate justification) may become an onerous and crucialtask. In some contexts, a medical justification audit report 765 mayinclude data 764 (where available) supporting care decisions made onbehalf of many individuals each of whom was readmitted (hospitalizedmore than once for a particular condition, e.g.). Alternatively oradditionally, in some contexts, such an association 776 (between the“second” patient 992 and an indication 777 of apparently-excessiveinstitutional readmissions, e.g.) may be established by an electronicrequest 771 (received from remote requestor 993 and directly invokingretrieval module 925, e.g.). More generally, such actions taken withreference to one or more criteria are “selective” (as used in FIGS.59-62 below, e.g.) if at least one of the criteria is used as adeterminant in deciding which data components (records, e.g.) will notbe included in or affected by the action.

With reference now to FIG. 10, shown is another example of a system 10in which one or more technologies may be implemented. One interface 1001(e.g. a desktop system 841, 941) is configured for use (e.g. by aphysician, administrator, or other authorized entity 1091) in enteringand transmitting an order 1018 or other such content (of a protocol 130or condition 170, e.g.) via one or more networks 1090 as describedabove. The one or more networks 1090 are also configured to contactentity 1091 (using contact information 720 for the same interface 1001or another interface 1002 associated with the same entity 1091, e.g.)under some conditions as described herein, such as to request anindication of the effectiveness of a treatment (protocol 130, e.g.) thatthe entity might have tried or witnessed recently. In some contexts,this permits protocol data 1090 (average evaluations 1053 or use counts1054, e.g.) to be generated or updated (on various instance of media105, 405, 505, 605, 705 in network 1050, e.g.).

With reference now to FIG. 16, shown is a high-level logic flow 16 of anoperational process. Intensive operation 36 describes obtaining anindication of a first protocol being employed in relation to aparticular condition in a first patient (e.g. input module 313 receivinga record 564 indicating that an order 1018 was placed for a particulardrug 141 or protocol 140 prescribed or purchased for the treatment of aparticular condition 170 in patient 250). This can occur, for example,in a context in which device 305 includes one or more media 105 (onnetwork 1090, e.g.) bearing an average evaluation 1053, use count 1054,or other such quantified protocol data 1050 as described below (as adata component 147 associated with the particular condition 170 and withthe particular drug 141 or protocol 140, e.g.). In some contexts,moreover, input module may receive the indication as an inquiry into theprospect of treating condition 170 with one or more protocols 130, 140and may record such inquiries in record 564. Alternatively oradditionally, input module 313 and request module 332 may be configuredto perform operation 36 jointly by initiating communication with someonegenerally familiar with the protocol 140 (a nurse or pharmacist who canadminister the particular drug 141 or protocol 140, e.g.).

Extensive operation 63 describes requesting an effectiveness indicationof the first protocol from an entity partly based on the entityvalidating the first protocol and partly based on a first communicationdelay associated with the first protocol, the first communication delayexceeding one hour (e.g. request module 331 asking one or more entities1091 who validated the particular protocol for an effectivenessindicator 456 signaling how effective the particular protocol was forthe treatment of condition 170 in patient 250). This can occur, forexample, in a context in which an entity 1091 signals one or morevalidations 701, 702 of the treatment by prescribing, purchasing,administering, or authorizing the particular drug 141 or protocol 140for the treatment of condition 170 in patient 250 and in which one ormore data components 127, 137, 147 define respective communicationdelays 542, 543, 544 so that request module 331 transmits a query (bytelephone or e-mail, e.g.) to the entity 1091 (practitioner or patient,e.g.) only after the treatment has probably failed or started to work.In a context in which a 10-day course of an antibiotic (as protocol 130,e.g.) would be expected to alleviate a fever (as condition 160, e.g.) ina few hours or days, for example, a corresponding communication delay543 of about 5 days (within an order of magnitude, e.g.) will beappropriate for obtaining a score 455 (on a 0-5 scale, e.g.) or othereffectiveness indicator 456 as a delayed automatic response to theordering or administration of the antibiotic. In less urgent contexts,moreover, an expected delivery time (in hours or days, e.g.) may beincluded for some of the communication delays 541-544 (those for which adrug 141 or other material component of a protocol 140 is delivered to apatient's home 289, e.g.). Alternatively or additionally, request module331 may be configured to send the same request to a particular entity1091 via more than one interface 1001, 1002 (using both an e-mailaddress 721 and a telephone number 722 associated with a singleidentified entity 1091, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for transmitting queries or other information requests asdescribed herein without undue experimentation. See, e.g., U.S. Pat. No.8,073,013 (“Method and apparatus for collecting survey data via theinternet”); U.S. Pat. No. 7,962,359 (“Method and system for collectingand disseminating survey data over the internet”); U.S. Pat. No.7,836,073 (“Method and system for transmitting pre-formulated query todatabase”); U.S. Pat. No. 7,590,547 (“Method for transmitting ananonymous request from a consumer to a content or service providerthrough a telecommunication network”); U.S. Pat. No. 7,529,214 (“Mobilenode for transmitting a request for information which specifies atransfer device to be used”); U.S. Pat. No. 6,807,532 (“Method ofsoliciting a user to input survey data at an electronic commerceterminal”); U.S. Pat. No. 6,513,014 (“Method and apparatus foradministering a survey via a television transmission network”).

Extensive operation 67 describes signaling a decision whether to updatea prominence indication of the first protocol in response to whether theeffectiveness indication of the first protocol was received from theentity after the effectiveness indication is requested from the entitypartly based on the entity validating the first protocol and partlybased on the first communication delay associated with the firstprotocol (e.g. statement module 382 incrementing a use count 1054 inresponse to receiving a Facebook-style “like” signal from a patient 250who used the protocol). This can occur, for example, in a context inwhich the patient 250 was the “entity” contacted in operation 63 (viacontact information 720, e.g.); in which the patient 250 was sent arequest for such a “like” signal after protocol 140 had enough time (tofail or start working, e.g.), in which a total count of such “like”signals is a “prominence indication” (of protocol 140, e.g.), in whichthe communication delay and the “first” patient's identity are recordedbut not published, and in which a new best practice could not otherwisewin widespread recognition within a year of someone devising thepractice. In some contexts, for example, a nurse or other care providerfamiliar with one or more protocols 120, 130 (as they apply to condition160, e.g.) can designate one or more corresponding delays (based on asuccess, when a difference is typically seen, or on a side effect onsetor other symptom change distribution, e.g.). In a context in whichprotocol 120 comprises a spinal fusion, for example, a correspondingdelay 2226 may be between 6 and 12 months. (See FIG. 22.) In a contextin which protocol 130 comprises administering an antihypertensive (forcondition 170, e.g.), a corresponding delay 2237 may be on the order of1.0 months (within an order of magnitude, e.g.). Alternatively oradditionally, statement module 382 may perform operation 67 bytransmitting an average evaluation 1053 computed based oneffectiveness-indicative numerical scores 455 received from each ofseveral entities 1091. This can occur, for example, in a context inwhich multiple entities have each responded to a corresponding query 573(like “We need to know how effective you thought this treatment was on azero-to-five scale . . . please press or say ‘5’ to indicate that thetreatment was perfectly effective . . . please press or say ‘0’ toindicate that the treatment was completely ineffective,” e.g.)transmitted by request module 331 and in which such an average (as arolling or inception-to-date average, e.g.) is a “prominence indication”of the treatment or other protocol.

With reference now to FIG. 11, shown is another example of a system 11(a subsystem of one or more networks described above, e.g.) in which oneor more technologies may be implemented. A local unit 1105 owned or usedby a caregiver 1191 may be configured to receive one or more orders1018, 1118 or other indications 1126, 1127, 1136, 1137 each comprisingcorresponding data components 126, 127, 136, 137 that each relate to acorresponding specific combination of a condition 160, 170 and protocol120, 130 for its treatment, as shown. In some contexts, one or moreservers 1195 (residing in networks described herein, e.g.) or localcircuitry may provide selective feedback (one or more warnings 1119,e.g.) relating to some such combinations (selected by caregiver 1191,e.g.).

With reference now to FIG. 17, shown is a high-level logic flow 17 of anoperational process. Intensive operation 37 describes obtaining anassociation between a particular condition and a first protocol (e.g.input module 311 receiving a record 563 indicating that an order 1118was placed for a particular drug or protocol 130 prescribed or purchasedfor the treatment of a particular condition 160). This can occur, forexample, in a context in which the protocol 130 includes administeringprednisone daily by ingestion and in which the particular condition 160is Bell's palsy, bone pain, carpal tunnel syndrome, muscular dystrophy,pulmonary fibrosis, or certain other off-label uses of prednisone. Insome contexts, moreover, such protocols 120, 130, 140 may include otherdrugs or non-medicinal components (physical therapy or surgery, e.g.).Moreover input module 311 may, in some variants, be configured to beinvoked by one or more queries 571-574 or other structured dialogs(permitting an expert system 393 to interact with a physician or othercaregiver 1191 via local unit 1105, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for searching for therapies or conditions that may apply to apatient as described herein without undue experimentation. See, e.g.,U.S. Pat. No. 8,008,285 (“Droxidopa and pharmaceutical compositionthereof for the treatment of fibromyalgia”); U.S. Pat. No. 8,005,687(“System, method and computer program product for estimating medicalcosts”); U.S. Pat. No. 7,979,289 (“System and method for intelligentmanagement of medical care”); U.S. Pat. No. 7,860,552 (“CNS assay forprediction of therapeutic efficacy for neuropathic pain and otherfunctional illnesses”); U.S. Pat. No. 7,797,145 (“Animal healthdiagnostics”); U.S. Pat. No. 7,552,039 (“Method for sample processingand integrated reporting of dog health diagnosis”); U.S. Pat. No.7,490,048 (“Apparatus and method for processing and/or for providinghealthcare information and/or healthcare-related information”); U.S.Pat. No. 7,346,523 (“Processing an insurance claim using electronicversions of supporting documents”); U.S. Pat. No. 6,704,595 (“Automatedmethod for diagnosing and monitoring the outcomes of atrialfibrillation”); and U.S. Pat. No. 6,014,626 (“Patient monitoring systemincluding speech recognition capability”).

Intensive operation 44 describes causing a comparison between athreshold and a prominence indication of treating the particularcondition with the first protocol after the association between thenparticular condition and the first protocol is obtained (e.g. invocationmodule 373 triggering comparator 391 to generate an output 195 bycomparing a prominence indication 1136 with a threshold 191). This canoccur, for example, in a context in which one or more devices 305(including media 105, 405, 505, 705, e.g.) reside in server 1195 and inwhich response module 351 selects the threshold 191 according to whoinitiates the association (as a function of a user identifier 523 of aspecific caregiver 1191 or caregiver type, e.g.) or to what condition160 or protocol 130 has been associated. In some contexts, for example,more esteemed caregivers or less hazardous conditions and protocols maywarrant a threshold 192 corresponding to a lower prominence (signalingless scrutiny and more latitude in the caregiver's choice of treatmentprotocols, e.g.). Alternatively or additionally, invocation module 373may trigger a comparison implemented in a formula (as a subtraction,e.g.). In some contexts, moreover, a less-prominent protocol may berequested by a patient 250 or warranted by the patient's situation.Alternatively or additionally, invocation module 373 may be configuredto trigger a storage operation in which one or more instances ofprominence indications 1136; thresholds 191; comparison results;quantifications of reputation or scrutiny or latitude (characterizingcaregiver 1191, e.g.); or other output 195 are stored in one or morerecords 569-569, 671-675 as described herein (e.g. in a data component136-138, 146-148 relating to an elected protocol 130, 140).

Extensive operation 64 describes signaling a decision whether to cautiona caregiver partly based on the association between the particularcondition and the first protocol and partly based on the comparisonbetween the threshold and the prominence indication of treating theparticular condition with the first protocol (e.g. response module 356transmitting an “obscure treatment option” warning 1119 to caregiver1191 if the threshold 191 exceeds the prominence indication 1136 andotherwise not transmitting any such warning). This can occur, forexample, in a context in which server 1195 is on several networks 290,890, 990; in which searching various records archives 820, 920 can takeseveral minutes or hours to determine a prominence indication 1136; inwhich local unit 1105 includes an e-mail or other text message displaycapability operable to deliver such warnings; in which a hospital 201 orfield of practice uses a standard numerical threshold for all prominenceindication comparisons; and in which the caregiver 1191 would otherwiseselect among several protocols 120, 130 for the particular condition(s)160, 170 without knowing which of them had recently become popular inthe caregiver's field of practice. In a context in which highernumerical indications 1126 signify more prominence and in which athreshold is set at 4, for example, such threshold may be met(sufficient to avoid triggering a cautionary message to caregiver 1191,e.g.) by determining either that 4 instances of condition 160 had beentreated with protocol 120 (for an implementation incorporating a usecount 1054, e.g.) or that one or more entities indicated theeffectiveness of treating condition 160 with protocol 120 with anaverage evaluation of at least 4 (for an implementation incorporating anaverage evaluation 1053, e.g.). Alternatively or additionally, responsemodule 356 may be configured to implement a conditional decision tocaution a caregiver 1191 with one or more of a font effect (a bolding orbright color selectively applied for lower-prominence therapies, e.g.),audible warning 1119 (a tone, e.g.), or modal dialog box (displaying amessage like “are you sure you want to order this unconventionaltreatment?” at local unit 1105 before finalizing order 1118, e.g.).

With reference now to FIG. 12, shown is another example of a system 12(e.g. a subsystem of one or more networks 290, 890, 990, 1090, 1290) inwhich one or more technologies may be implemented. A motor vehicle orother device 1241 associated with a care administration space (alocation 1204 inside or near ambulance 1295 configured to permit one ormore caregivers 1291 to treat a patient 1292 in trauma, e.g.) mayinclude one or more instances of wireless transceivers 1211, wallmountings 1213, display screens 1216, or couplings 1218 to externalpower. Also in some contexts, as described below, device 1241 may beconfigured to obtain and present one or more medical records 1217(comprising one or more data components 126, 128 relating to anemergency protocol 120 or to a specific patient 1292 relayed via displayscreen 1216, e.g.). This can occur, for example, in a context in which awrist band 1223 or other device 1242 worn or held by patient 1292contains one or more implementations of conditional consent 1222(configured by patient 1292 prior to an emergency, e.g.) or transponders1225 as described below.

With reference now to FIG. 18, shown is a high-level logic flow 18 of anoperational process. Intensive operation 39 describes obtaining anassociation between a care administration space and a first device (e.g.configuration module 322 making a record 568 in which an identifier 734of the “first” device 242, 1241 is associated with an identifier 732 ofan ambulance 1295 or other location 204 allocated to providing patients250 medical care). This can occur, for example, in a context in which“first” device 242, 1241 includes a wall mounting 1213 fixing it inrelation to the care administration space; in which the “first” deviceincludes a wireless transmitter 394 or transceiver 1211 detectable by a“second” device as described below; and in which the care administrationspace is defined by the effective range of the wireless transmitter 394or transceiver 1211. In some contexts, for example, such locations 204may include an emergency room or urgent care clinic. Alternatively oradditionally, a regional server 1195 or other stationary device innetwork 1290 may be configured to obtain GPS data 751 indicating acurrent position of an ambulance 1295 or other mobile careadministration space that may then be compared with GPS data 752indicating a current position of a device held or worn by patient 250(e.g. through network 1290 in lieu of direct wireless transmissionbetween proximate devices 1241, 1242). In some contexts, moreover, the“first” device may comprise an external power coupling 1218 configuredto power the “first” device for an indefinite period (via a vehiclebattery or similar source that is maintained daily, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for configuring a device for direct or indirect wirelesscommunication as described herein without undue experimentation. See,e.g., U.S. Pat. No. 7,986,940 (“Automatic wireless network linkingmethod with security configuration and device thereof”); U.S. Pat. No.7,940,744 (“System, apparatus and method for automated wireless deviceconfiguration”); U.S. Pat. No. 7,929,950 (“Dynamically configurable IPbased wireless device and wireless networks”); U.S. Pat. No. 7,916,707(“Identity-based wireless device configuration”); U.S. Pat. No.7,885,687 (“Device for updating configuration information in a wirelessnetwork”); U.S. Pat. No. 7,778,752 (“System for connecting a telematicsdevice to a vehicle using a wireless receiver configured to transmitdiagnostic data”); U.S. Pat. No. 7,681,231 (“Method to wirelesslyconfigure a wireless device for wireless communication over a securewireless network”); U.S. Pat. No. 7,643,828 (“Method and apparatus forfast link setup in a wireless communication system”); U.S. Pat. No.7,616,594 (“Wireless device discovery and configuration”); and U.S. Pat.No. 7,233,745 (“Field device configured for wireless datacommunication”).

Intensive operation 46 describes obtaining via a second device a patientconsent conditionally authorizing a release of a first medical record,the second device being a mobile device (e.g. input module 315 receivingpre-emergency input 551 from or about a patient 492 that includes aconditional consent 1222 permitting a release of the one or more medicalrecords 567, 1217 of the patient's to a caregiver 991, 1291 that iscontingent upon the occurrence of an emergency). This can occur, forexample, in a context in which the patient 492 (who can, in someinstances, be the same individual as one or more other identifiedpatients depicted herein, e.g.) enters such pre-emergency input 551 (bya menu selection, e.g.) using a handheld device (the “second” device1242, e.g.); in which the “occurrence of an emergency” is manifested asthe “second” device entering the “care administration space” (e.g.location 204, 1204); and in which the authorization to release the“first” medical record would otherwise be much slower (due to trauma,e.g.). In some contexts, for example, the “first” device may beconfigured to include one or more media 105, 505 bearing suchcontingently-releasable medical records 1217 for most or all registeredpatients 992, 1292 (patients enrolled in registry 109, e.g.) in a region(county or state, e.g.) so that the “first” and “second” devices 1241,1242 may easily interact directly and locally (not via network 1290,e.g.) with or without network 1290 being online. Alternatively oradditionally, the “second” device may include a wrist band 1223 wearableby an at-risk patient 1292 (e.g. one suffering from dementia, epilepsy,or other medical conditions that make it more likely that a patient maybe unable to consent to a records transfer).

Extensive operation 66 describes invoking circuitry for causing thefirst device to receive the first medical record partly based on thesecond device entering the care administration space and partly based onthe patient consent authorizing the release of the first medical record(e.g. invocation module 372 causing display screen 1216 of device 1241to display medical record 1217 as an automatic response to the “second”device 1242 entering the care administration space and partly based onthe prior configuration of above-described conditional consent 1222 (inoperation 46, e.g.). In some contexts, for example, such configurationmay have been implemented by a non-emergency caregiver 991 who providesthe patient with the “second” device 1242. Alternatively oradditionally, in some contexts, a local entity (a hospital 201 orambulance company, e.g.) may own the first device, a patient may own thesecond device, and a third entity may own the invoked “circuitry.”

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for identifying wireless devices in a region of interest asdescribed herein without undue experimentation. See, e.g., U.S. Pat. No.7,903,905 (“Pen-shaped scanning device having a region identitysensor”); U.S. Pat. No. 7,869,807 (“Method of managing a codeidentifying a wireless device with conflict minimized in a wirelesstelecommunications system”); U.S. Pat. No. 7,319,876 (“System and methodfor using equipment identity information in providing location servicesto a wireless communication device”); U.S. Pat. No. 7,295,120 (“Devicefor verifying a location of a radio-frequency identification (RFID) tagon an item”); U.S. Pat. No. 6,791,477 (“Method and apparatus foridentifying waypoints and providing keyless remote entry in a handheldlocator device”); U.S. Pat. No. 6,693,512 (“Device location andidentification system”); and U.S. Pat. No. 6,392,747 (“Method and devicefor identifying an object and determining its location”).

With reference now to FIG. 13, shown is another example of a system 13(e.g. a subsystem of one or more networks 290, 890, 990, 1090, 1290) inwhich one or more technologies may be implemented. As shown, caregiver1391 wears a device 1342 (on a lanyard or clothing 1349, e.g.)configured to include a caregiver identifier 1332 that identifies her.Likewise patient 1331 wears a device 1341 configured to include apatient identifier 1331 that identifies him (on a gown or wrist band1223, e.g.). In some variants, such wearable devices 1341, 1342 areconfigured to interact wirelessly (either with one another or with awall-mounted device 1343, e.g.) as an automatic response to being in acommon location (e.g. at location 1204, 1304).

With reference now to FIG. 19, shown is a high-level logic flow 19 of anoperational process. Intensive operation 38 describes obtaining anindication of a first device associated with and wearable by a patienthospitalized for a particular condition (e.g. configuration module 322associating a specific patient 1392 with a patient identifier 1331 on anarticle wearable by a patient 1392 who has been admitted to hospital 201for a specific pathology 181 or complaint 513). This can occur, forexample, in a context in which the article (a wrist band 1223, e.g.) isassigned to patient 1392 upon checking in to the hospital; in whichconfiguration module 322 was invoked at that time (at patient intake,e.g.); and in which one or more instances of device 305 reside on one ormore networks described herein (in a wall-mounted device 1343 or server1195 of hospital 201, e.g.). Alternatively or additionally, a stationarydevice 1343 may perform operation 38 by detecting a device 1341associated with patient 1392 in a given location 1304 (entering hishospital room, e.g.).

Intensive operation 41 describes obtaining an indication of a seconddevice associated with and wearable by a caregiver (e.g. configurationmodule 321 associating a specific caregiver 1391 with a caregiveridentifier 1332 on an article wearable by the caregiver). This canoccur, for example, in a context in which the article (on a badge orlanyard or in a wrist band or article of clothing 1349, e.g.) wasassigned to caregiver 1391 upon arriving at the facility and in whichconfiguration module 321 was invoked at that time. Alternatively oradditionally, a stationary device 1343 (mounted on a wall, e.g.) mayperform operation 41 by detecting a device 1342 associated withcaregiver 1391 in a given location 1304 (entering her patient's hospitalroom, e.g.).

Intensive operation 45 describes causing a recordation of a timestamp asan automatic response to the first device associated with and wearableby the patient and the second device associated with and wearable by acaregiver both being in a single common location (e.g. configurationmodule 324 storing a timestamp 711 indicating when both caregiver 1391and patient 1392 were together in location 1304). This can occur, forexample, in a context in which timestamp 711 is generated from a digitalclock 392; in which record 710 is initially aggregated at one or moredevices 1341-1343 locally, in which one or more records archives 820,920 later received record 710 in a batch data aggregation process, andin which the “single common location” is a hospital room or a detectionrange of one or more devices 1341-1343. In some implementations, forexample, device 1341 may include one or more configuration modules321-326 as described herein and may be configured to perform operations38, 41, and 45 (in lieu of device 1343, e.g.). Alternatively oradditionally, in some variants, device 1342 may likewise include one ormore configuration modules 321-326 as described herein and may beconfigured to implement device 305 (e.g. operable to perform operations38, 41, and 45).

Extensive operation 65 describes causing a retrieval of the timestamp inresponse to an indication of an institutional readmission after therecordation of the timestamp indicating the first device associated withand wearable by the patient and the second device associated with andwearable by the caregiver both having been in the single common location(e.g. response module 352 retrieving a record 710 including such timingdata 453 from one or more records archives 820, 920 in response to arequest 581 indicative of patient 1392 being readmitted to one or morehospitals 201, 202 for the same specific pathology 181 or complaint513). This can occur, for example, in a context in which suchreadmission for the particular condition would otherwise trigger areduction in payment for one or more prior hospitalizations. In somecontexts, for example, one or more remote requestors 893, 993 may haveinitiated a prior instance of operation 65 (performed by a remoteinstance of invocation module 371, e.g.) in which an entity's request581 for records included a readmission-indicative report type 521(having a name that includes “readmission,” e.g.), areadmission-indicative request authorization 522 (from an agency thatmonitors excessive readmissions, e.g.), a query reciting or prompted byreadmission, or other such explicit or implicit indications 525 ofreadmission that might have been avoidable if a prior hospitalization ortreatment had been executed correctly. Alternatively or additionally,response module 352 may be configured to perform operation 65 byretrieving and transmitting such a timestamp-containing record 710(indicative of when the first and second devices 1341, 1342 were both inthe single common location 1304, e.g.) to one or more remote requestors893, 993.

With reference now to FIG. 20, shown is context in which one or moretechnologies may be implemented. System 2000 may include two or moredevices 2005, 2015 having a linkage 2011 therebetween as describedherein. In various embodiments, device 2005 may include one or moreinstances of lookup modules 2021, 2022; update modules 2028, 2029;detection modules 2041, 2042, 2043, 2044, 2045, 2046; cameras 2053 orother sensors 2054; or processors 2055 as described below. Alternativelyor additionally, device 2005 may comprise a machine 2030 (configured forvending or other dispensations of drugs 141, foods, or other goods 691,e.g.); a battery or other on-board power supply 2058; or one or morespeakers 2057 (configured to manifest a warning 1119 or other audio data2257 as described below, e.g.). In various implementations, device 2015may likewise include one or more instances of food containers(refrigerators or cupboards 2071, e.g.); actuators 2072 (of a dispenser,e.g.); exercise machines 2073 (relating to one or more regimens2331-2339, e.g.); handhelds 2074 (telephones, e.g.); detectablestructures 2075 (transponder or barcode, e.g.); adhesives 2077;wristbands 2078; or buttons 2079. Alternatively or additionally, device2015 may comprise medical equipment 2080 (devices configured for imagingor measurement, e.g.). One or more of devices 2005, 2015 may beconfigured to implement an instance of device 305 and to include one ormore media depicted herein. See FIGS. 1, 4-7 and 21-26.

With reference now to FIG. 21, shown is context in which one or moretechnologies may be implemented. System 2100 includes one or moredata-handling media 2105 (residing in an instance of device 305, e.g.)operably coupled with one or more search engines 2198 on the variousnetworks described herein. Medium 2105 may include one or more instancesof search terms 2110 (e.g. comprising criteria 2101, 2102); names 2111,audit identifiers 2112, or other such indications 2113; search results2130; values 2161, 2162; or queries 2171, 2172 as described below.

With reference now to FIG. 22, shown is context in which one or moretechnologies may be implemented. System 2200 may (optionally) includeone or more data-handling media 2205 (configured to transmit or storedata, e.g.) residing in an instance of device 305 or otherwise on anetwork 290 as described above. In some variants, medium 2205 may bearone or more instances of zone description data 2217 (e.g. representingone or more service zones 207, 208 or other locations 204, 1204, 1304);data components 126, 127, 136, 137 (in tabular form, e.g.); reports2243, 2244, 2245; requests 2246; signals 2251, 2252, 2253, 2254(comprising audio data 2257 or other encoded data 2258, e.g.); searchterms 2280 (comprising one or more text strings 2281, 2282, 2283connected by logical operators, e.g.); messages 2290 (comprising phonecalls 2291, text 2292, and annotations 2293 as described below, e.g.);and hyperlinks 2296, menu options 2297, or other such controls 2295(comprising one or more interfaces 1001, 1002 or other devices describedabove, e.g.). In some contexts, data component 126 (as described above)may include one or more delays 2226 corresponding specifically to thehandling of condition 160 with protocol 120; data component 127 (asdescribed above) may include one or more delays 2227 correspondingspecifically to the handling of condition 170 with protocol 120; datacomponent 136 (as described above) may include one or more delays 2236corresponding specifically to the handling of condition 160 withprotocol 130; and data component 137 (as described above) may includeone or more delays 2237 corresponding specifically to the handling ofcondition 170 with protocol 130. Moreover in some variants each instanceof audio data 2257 may include one or more timestamps 711 as well asother data 712 (transcripts or labels of patient interview clips,recorded physician remarks, concurrent diagnostic data 490, or otherevents encoded as text 2292 or other annotations 2293 relating to rawauditory data with which they are archived, e.g.).

With reference now to FIG. 23, shown is context in which one or moretechnologies may be implemented. System 2300 may include one or moredata-handling media 2305 (configured to transmit or store data, e.g.)residing in an instance of device 305 or otherwise on a network 290 asdescribed above. In some variants, medium 2305 may bear one or moreinstances of triggers 2301, 2302, 2303, 2304; countdown timers 2310;results 2311, 2312, 2313, 2314, 2315; conditions 2321, 2322, 2323, 2324,2325, 2326, 2327, 2328, 2329; regimens 2331, 2332, 2333, 2334, 2335,2336, 2337, 2338, 2339; indications 2341, 2342, 2343, 2344, 2345, 2346,2347, 2348, 2349; terms 2351, 2352, 2353; patterns 2361, 2362, 2363,2364, 2365, 2366; prompts 2371, 2372, 2373, 2374, 2375, 2376, 2377,2378, 2379; coordinates 2381, 2382; or other such user interactioncontent or programmatic determinants 2391, 2392, 2393, 2394, 2395affecting automatic decisions as described herein.

With reference now to FIG. 24, shown is context in which one or moretechnologies may be implemented. System 2400 may include one or moredata-handling media 2405 (configured to transmit or store data, e.g.)residing in an instance of device 305 or otherwise on a network 290 asdescribed above. In some variants, medium 2405 may bear one or moreinstances of maps 2423 or similar positional graphics; screen displays2426 or ink-printed surfaces 2427; protocols 2440 or other task lists2445 (comprising one or more time intervals 2545 associated with one ormore tasks 2441, 2442, 2443, 2444, e.g.); thresholds 2451, 2452, 2453,2454, 2455, 2456; responses 2458, 2459; performance metrics 2461, 2462,2463, 2464; inputs 2471, 2472, 2473, 2474; or other indications 2481,2482, 2483, 2484, 2485, 2486, 2487, 2488, 2489 (as user interactioncontent or programmatic determinants affecting automatic decisions asdescribed herein, e.g.).

With reference now to FIG. 25, shown is context in which one or moretechnologies may be implemented. System 2500 may include one or moredata-handling media 2505 (configured to present or otherwise transmitdata, e.g.) residing in an instance of device 305 or otherwise on anetwork 290 as described above. In some variants, medium 2505 may bearone or more instances of designations 2501, 2502; decisions 2508, 2509;orders 2511, 2512, 2513, 2514, 2515, 2516; biometric data 2540(comprising a fingerprint pattern 2531 or audible pattern 2532, e.g.);intervals 2541, 2542, 2543, 2544, 2545; indications 2551, 2552, 2553,2554, 2555, 2556, 2557, 2558, 2559; signals 2561, 2562, 2563, 2564,2565; or images 2575, 2576, 2577, 2578, 2579, 2580 (comprisingrespective image portions 2581, 2582, 2583 and a remainder, e.g.).

With reference now to FIG. 26, shown is a system 2600 in which one ormore technologies may be implemented. System 2600 may include one ormore incentives 2640 represented or manifested (as voltage levels ormagnetization states comprising digital expressions, e.g.) on magneticor other storage media 2652, display media 2654, transmission media2656, or other media 2605. In some contexts, such expressions mayexplicitly associate an actual (accomplished) or prospective incentive2640 that is physical and tangible: a card or other device-readablemedium granting a membership or other temporary access for one or moreincrements 2611, 2612, 2613 of time; cash or other certificatesindicative of points 2616, credits 2617 or other physical media ofexchange; medications, nutritional supplements, exercise equipment, orother goods transferred as payments in kind 2618; or other suchresources 2619 directly manifesting a physical, tangible benefit 2620 as(at least part of) the incentive. Alternatively or additionally, suchincentives can include one or more discounts or other terms 2631, 2632or conditions 2634, 2635; performance ratings 2638 or favorablereferrals 2641, 2642; policies, rebates, or other eligibilities 2646,2647; or supplemental therapies or other such services 2648. In somecontexts, as exemplified below, a combination of such incentives may benecessary or helpful for motivating qualified patients to comply with atesting or treatment regimen 2331-2339 or for motivating others toexplain or otherwise facilitate an individual's participation orenrollment in a testing or treatment program. Alternatively oradditionally, one or more of the above-described devices may includemedium 2605 and may access or be accessed by a network 2690. In somecontexts, for example, a portable computer 2670 or similar userinterface 1001 residing in network 2690 may comprise one or more outputs2671 or inputs 2672 (operable for entering or accessing one or moreorders 2511-2516 or other user data, e.g.) as shown.

In light of teachings herein, numerous existing techniques may beapplied for identifying and administering tangible or other incentiveseffectively to motivate individuals to suggest or elect products orprograms as described herein without undue experimentation. See, e.g.,U.S. Pat. No. 7,739,115 (“Script compliance and agent feedback”); U.S.Pat. No. 7,668,747 (“System and method for providing incentives topurchasers”); U.S. Pat. No. 7,653,594 (“Targeted incentives based uponpredicted behavior”); U.S. Pat. No. 7,624,051 (“Method and system forforming a list-based value discovery network”); U.S. Pat. No. 7,555,444(“Dynamic time-of-purchasing-decision incentive system and method”);U.S. Pat. No. 7,433,834 (“Apparatus and method for facilitatingtransactions”); U.S. Pat. No. 7,389,245 (“Method and apparatus forproviding incentives to physicians”); U.S. Pat. No. 7,376,700 (“Personalcoaching system for clients with ongoing concerns such as weight loss”);U.S. Pat. No. 7,373,318 (“Information recommendation apparatus andinformation recommendation system”); U.S. Pat. No. 7,016,854 (“Loyaltylink method and apparatus with audio performance for integratingcustomer information with dealer management information”); U.S. Pat. No.6,988,132 (“System and method for identifying and establishing preferredmodalities or channels for communications based on participants'preferences and contexts”); U.S. Pat. No. 6,952,678 (“Method, apparatus,and manufacture for facilitating a self-organizing workforce”); U.S.Pat. No. 6,901,347 (“Availability, reliability or maintainability indexincluding outage characterization”); U.S. Pat. No. 6,739,508(“Evaluation apparatus with voting system, evaluation method with votingsystem, and a computer product”); U.S. Pat. No. 6,699,124 (“Amusementgame incentive points system”); U.S. Pat. No. 6,561,811 (“Drug abuseprevention computer game”); and U.S. Pat. No. 5,537,314 (“Referralrecognition system for an incentive award program”).

With reference now to FIG. 27, shown is a network 2790 having wirelesssignal paths or other suitable linkages 2706, 2726, 2756, 2776 providingaccess among several parties. An insurer, policymaker, programenrollment coordinator, or similar service provider 2710 may have accessthrough a control unit 2705, for example, implementing a local displaymodule or other media 2605 as described herein. One or more supporttechnicians 2761, program enrollment coordinators, or other such agents2762 may similarly access or provide data through network 2790 viaservers or other response units 2755 implementing media 2605.Individuals 2782 prospectively or actually participating in atherapeutic or monitoring regimen 2331-2339 as described herein maysimilarly communicate with others on network 2790 via a portable orother local interaction unit 2775. Material providers 2781 or careproviders 2783 having regular opportunities to interact personally withsuch individuals 2782 may likewise have local interaction units 2775operable for indicating compliance, enrollment, or similar events to betracked pursuant to therapeutic components (products or otherrequirements of a prescribed regimen, e.g.) or artificial incentives2640 as described herein. Alternatively or additionally, correspondenceor incentive deliveries to one or more beneficiaries 2721 or otherrecipients 2722 may occur automatically via one or more delivery units2725 as described herein. Any such control units 2705, delivery units2725, response units 2755, or interaction units 2775 may (optionally)include one or more storage media 2652, display media 2654, transmissionmedia 2656 or other modules indicating, delivering, or otherwisemanifesting one or more (artificial) incentives 2640 as describedherein. In some variants, moreover, such devices or networks 2790 mayinclude one or more invocation modules 371-374, 2795 (for facilitatingone or more flows, e.g.) as described herein.

With reference now to FIG. 28, shown is a system 2800 in which one ormore technologies may be implemented. A bottle 2883, capsule 2884, orother vessel 2890 may include one or more plungers 2862, slidable orother covers 2861, buttons 2863, removable caps, or other actuators2870. Such administration detection features 2880 may be configuredeffectively to permit one or more primary modules 2810 to monitoradministrations (of a therapy, e.g.) within a vicinity of a vessel 2890,transdermal delivery device, iontophoretic device, patch withmicroprotrusions, dispenser, or other such object (variants of articlesdepicted below in FIGS. 29-47, e.g.). In some variants, for example, oneor more transmitters 2876 on such dispensers permit periodic oroccasional notifications (via a wireless or other coupling 2855 with aprimary module 2810, e.g.) of such administrations (detected via one ormore sensors 2877 of the vessel 2890, e.g.) or a remaining quantity ofmaterial (nominally or actually) available for dispensation.Alternatively or additionally, a colorant or other marking component2879 permits direct optical or auditory monitoring (of a vessel ormaterial, e.g.) within a vicinity of the dispenser or of a recipient2722 of the therapy. Such systems may likewise include or otherwiseinteract with a vessel 2890 or other object containing one or morebioactive materials or other therapeutic components: medications,nutraceuticals, placebos, inhalants, inoculants or other such materials.

In some variants, a service delivery unit may include one or moreprimary modules 2810 having one or more instances of incentivenegotiation modules 2820, recording systems 2830, user interfaces 2840,regimens 2847, administration detection modules 2848, modules forconditioning an incentive upon compliance with a regimen 2849, oradministration detection features 2880 as described herein. In somecontexts, for example, incentive negotiation module 2820 may handle oneor more instances of signals 2816 indicative of one or more incentives2811, 2812. Alternatively or additionally, such a module may handle oneor more signals 2817 indicative of enrollment certification or signals2818 indicative of informed consent (from an individual participating ina program described herein, e.g.). Recording system 2830 may include acamera 2832 or other sensor 2833 (capable of capturing a visual record2836 or other data record 2835 confirming an administration or otherrelevant event as described herein, e.g.). An auditory sensor 2834 maylikewise capture an audio record 2837 or other data record 2835confirming a notification, enrollment, acceptance, transfer, or otherrelevant event as described herein. See also U.S. patent applicationSer. No. 13/066,444 (“Cost-effective resource apportionment technologiessuitable for facilitating therapies”).

With reference now to FIG. 29, shown is a system 2900 in which one ormore technologies may be implemented. Local event-sequencing logic 2905(comprising control unit 2705 or interaction unit 2775, e.g.) may beconfigured to interact with or monitor or otherwise detect one or morearticles 2910 having an RFID transponder 397 or ink-printed surface 2427or other device-readable feature (barcode 2918, e.g.). As variouslydescribed above, for example, such articles may comprise a patientidentifier 1331, caregiver identifier 1332, wearable article (wristband2078, e.g.), or other such device or system. In some contexts, moreover,article 2910 may comprise a device 2005 that includes one or morecameras 2053 or other sensors 2054 or special-purpose circuitry (forremote interaction via network 290, e.g.) as described herein.Alternatively or additionally, local event-sequencing logic 2905 mayitself comprise one or more instances of special-purposetransistor-based circuitry 2961, 2962, 2963 configured to provide aBoolean indication whether or not a patient needing a particular regimenhas been admitted to a qualifying institution; special-purposetransistor-based circuitry 2971 configured to select a playable promptin response to input from or about a patient; or special-purposetransistor-based circuitry 2972 configured to associate an individualwith a regimen. Alternatively or additionally, local event-sequencinglogic 2905 may comprise one or more regimen compliance determinations2986 or other compliance-positive indications 2987; regimennoncompliance determinations 2988 or other compliance-negativeindications 2989; or other such data distillations 2980 as describedherein (with reference to media, e.g.) at FIG. 1, 4-7, or 21-26 or inU.S. patent application Ser. No. 13/199,051 (“Systematic distillation ofstatus data relating to regimen compliance”).

With reference now to FIG. 30, shown is a system 3000 in which one ormore technologies may be implemented. Local event-sequencing logic 3005(operably coupled with and local to event-sequencing logic 2905, e.g.)may be configured to interact with a sample tester 3060 (configured toperform a compliance-monitoring or other diagnostic test upon a blood orother fluid sample from a patient, e.g.) or other medical equipment 2080residing in network 3090. As variously described herein, for example,such tests may be required by one or more regimens 2331-2339 or orders2511-2516 (prescribed or placed by a physician or other care provider2783, e.g.). In some contexts, moreover, local event-sequencing logic3005 may be configured to receive measurements or other results fromsample tester 3060 (as determinants 2391-2395 or other indications2341-2349 relating to decisions described herein, e.g.). Alternativelyor additionally, local event-sequencing logic 3005 may comprise one ormore instances of special-purpose transistor-based circuitry 3035configured to associate one or more tasks with a time interval;special-purpose transistor-based circuitry 3041, 3042, 3043, 3044configured to generate a Boolean indication whether or not an individualis compliant with a regimen; special-purpose transistor-based circuitry3051 configured to generate a Boolean indication whether or not apatient and a medical device are in proximity; special-purposetransistor-based circuitry 3052 configured to recognize a persondepicted in a portion of an image; or other relevant data as describedherein with reference to FIG. 1, 4-7, or 21-26.

With reference now to FIG. 31, shown is a system 3100 in which one ormore technologies may be implemented. Local event-sequencing logic 3105(operably coupled with and local to local event-sequencing logic 2905,e.g.) may be configured to access one or more records 3191-3197 residing(remotely, e.g.) in network 3190. As variously described herein, forexample, such records may include medical history data or otherbackground data (provided by or useful to material providers 2781 orcare providers 2783, e.g.). Alternatively or additionally, localevent-sequencing logic 3105 may comprise one or more instances ofspecial-purpose transistor-based circuitry 3115 configured to recognizea response after a prompt is played to an individual; special-purposetransistor-based circuitry 3121, 3122, 3123 configured to receive ascalar indication of how well an individual has complied with a regimen;special-purpose transistor-based circuitry 3131 configured to configuredto permit an individual to select among two or more portions of animage; or special-purpose transistor-based circuitry 3132 configured torecord an assignment of a resource as an automatic and conditionalresponse as described below.

With reference now to FIG. 32, shown is a system 3200 in which one ormore technologies may be implemented. Local event-sequencing logic 3205(resident in delivery unit 2725 or interaction unit 2775, e.g.) may beconfigured to monitor or control a portable material dispenser 3270(configured to perform a compliance-monitoring or incentiveimplementation task described below, e.g.) or both. As variouslydescribed herein, for example, such tasks may signify a component ofregimen compliance (dispensing a drug 141 on time, e.g.) or may manifestan incentive (candy dispensed as a payment in kind 2618 for enticing apatient or provider to cooperate, e.g.). Alternatively or additionally,local event-sequencing logic 3205 may comprise one or more instances ofspecial-purpose transistor-based circuitry 3261 configured to provide aBoolean indication whether or not an order associates a patient with amedical device; special-purpose transistor-based circuitry 3262configured to cause a countdown timer to progress; special-purposetransistor-based circuitry 3271 configured to notify an individual of anartificial incentive in response to a noncompliance indication; orspecial-purpose transistor-based circuitry 3273, 3274 configured toprovide a Boolean indication whether or not an individual is availableas described herein. See FIG. 34.

With reference now to FIG. 33, shown is a system 3300 in which one ormore technologies may be implemented. In some variants, medical deviceconfiguration logic 3305 (operably coupled with one or more instances ofevent-sequencing logic described above, e.g.) may be configured tocontrol one or more instances of an electrical or electromechanicaldisablement feature 3365 (a valve 3361 or fuse or latch 3362 configuredto enable/disable a primary function of medical equipment 2080 or otherdevices depicted herein, e.g.) in network 3390. As variously describedherein, for example, such features may prevent a dispensation or othermaterial transfer under some circumstances as described below. In somecontexts, moreover, medical device configuration logic 3305 may beconfigured to display or otherwise transmit decisions, determinants, anduser data via one or more media (depicted at FIG. 1, 4-7, or 21-26,e.g.). Alternatively or additionally, medical device configuration logic3305 may comprise one or more instances of special-purposetransistor-based circuitry 3311 configured to route an individual to aparticular destination as an automatic and conditional response;special-purpose transistor-based circuitry 3313, 3314 configured toinitiate an electronic intercommunication between individuals as anautomatic and conditional response; special-purpose transistor-basedcircuitry 3316, 3317 configured to cause a wearable article to indicatea data component as an automatic and conditional response;special-purpose transistor-based circuitry 3318 configured to retrieveand present medical data about a particular patient as an automatic andconditional response; special-purpose transistor-based circuitry 3322configured to compute an arithmetic combination of scalar indications;special-purpose transistor-based circuitry 3325 configured to transmit aBoolean indication whether or not a deadline was met; special-purposetransistor-based circuitry 3327 configured to enable a medical deviceselectively in response to a combination of indications; orspecial-purpose transistor-based circuitry 3328, 3329 configured toauthorize a dispensation if one or more specific conditions are met andotherwise generally not to authorize the dispensation. As explainedbelow, moreover, some or all such logic may be configured to respond todevice-detectable environmental or remote data irrespective of real-timelocal user input. See FIGS. 48-62.

With reference now to FIG. 34, shown is a system 3400 in which one ormore technologies may be implemented (in a server or other networksubsystem, e.g.). In some variants, primary unit 3405 may comprise oneor more instances of global positioning system (GPS) modules 3420(configured to generate coordinates 2381, 2382 in some variants, e.g.),search bots 3421, data distillation modules 3422, clip capture modules3426, speech recognition modules 3427, or text-to-speech translationmodules 3428. Such modules may reside in one or moreapplication-specific integrated circuits (ASICs), for example, or in ageneral purpose processor 2055 configured to execute special-purposesoftware (within a device 305 or system described above, e.g.).Alternatively or additionally, primary unit 3405 may implement a channelor other structure (comprising a linkage 2011 between devices, e.g.)within which one or more intercommunications 3441, 3442, 3443(comprising a call 3431, session 3432, dialog 3433, or otherbidirectional communication as described herein, e.g.) may exist asdescribed below. In some variants, moreover, such logic may comprise oneor more electrical nodes 3472, 3473, 3474, 3475, 3476, 3477, 3478, 3479,3480, 3481, 3482, 3483, 3484, 3485, 3486, 3487, 3488, 3489 (eachexpressing a yes-or-no decision or other Boolean value, e.g.). In somecontexts, for example, such nodes may each comprise a forked or othersignal path adjacent one or more logic gates, for example, the Booleanvalue manifested as either a “low” or “high” voltage according to acomplementary metal-oxide-semiconductor (CMOS), emitter-coupled logic(ECL), or other common semiconductor configuration protocol.

With reference now to FIG. 35, shown is a system 3500 in which one ormore technologies may be implemented. In some variants, interaction unit3505 (implemented local to an individual 2782 or service provider 2710,e.g.) may be configured to communicate via one or more instances of asatellite 3593 or other remote communication device in network 3590 (toone or more other networks described herein, e.g.). In some contexts,such interaction units 2775 may comprise one or more sensors 3506 (suchas a microphone 3508, e.g.) or speakers 3509 or other componentsoperable for handling data 3507 (for or from a patient, e.g.).Alternatively or additionally, interaction unit 3505 may comprise one ormore instances of special-purpose interface modules 3511, 3512, 3513,3514, 3515, 3516; selection modules 3531, 3532, 3533, 3534; ortriggering modules 3551, 3552, 3553, 3554, 3555, 3556 as describedbelow. As explained below, moreover, some or all such logic may beconfigured to respond to device-detectable environmental or remote datairrespective of real-time local user input. See FIGS. 48-62.

With reference now to FIG. 36, shown is a system 3600 in which one ormore technologies may be implemented. In some variants, response unit3605 (implemented local to a technician 2761 or care provider 2783,e.g.) may be configured to interact with an article 2910 (a sampletester 3060 or dispenser 3270 or other device 305 with a disablementfeature 3365, e.g.) in or via network 3690. In some variants sucharticles may comprise a disposable item 3695 (a syringe 3691 or inhaler3692 or infusion bag 3693 configured to be used only once, e.g.).Alternatively or additionally, response unit 3605 may comprise one ormore input modules 3621, 3622, 3623, 3624, 3625, 3626, 3627, 3628;response modules 3661, 3662, 3663, 3664; communication modules 3681,3682 or other control circuitry as described below.

With reference now to FIG. 37, shown is a system 3700 in which one ormore technologies may be implemented. In some variants, a computer 2670or other data-handling device 3705 may comprise one or moreconfiguration modules 3701, 3702, 3703, 3704; detection modules 3741,3742, 3743, 3744, 3745, 3746 (implementing a comparator 391 configuredto apply one or more patterns 2361-2366, e.g.); computation modules3771, 3772, 3773, 3774; or authorization modules 3791, 3792, 3793, 3794as described below. In some contexts, for example, data-handling device3705 may be implemented in a handheld device 305 (operably coupled to anearpiece 3749 or other wearable output device, e.g.) that also includesone or more cameras 3707 or other input devices (microphone 3708, e.g.)accessible to user 3780. Moreover such implementations may haveparticular utility in an institutional setting (comprising a stationarydevice 3760 mounted in a ceiling of a hallway 3709, e.g.). See FIG. 38.

With reference now to FIG. 38, shown is an example of a data-handlingdevice 3805 (worn or carried by a user 3880 in a nursing home 3802,e.g.) operably coupled (through a wireless or other linkage, e.g.) withone or more networks 3890 described herein. In some contexts, forexample, tabular data 3820 resident (on a server, e.g.) on network 3890may (optionally) include several records 3831-3834 each of whichincludes one or more status indicators 3842 or history data 3843 (orboth) designated by one or more record-designating patterns 3841(uniquely identifying each respective record, e.g.). In some variantsdata-handling device 3805 may include one or more badges 3851, bandages3852, identification tags 3853, or other positioning structures 3860 andmay include one or more diagnoses 3867, categories 3868, or otherindications 3870 (relating to user 3880 as a healthcare recipient 2722,e.g.). Alternatively or additionally data-handling device 3805 maycomprise an unpowered article 2910 with a barcode or other passivefeature readable by local event-sequencing logic 2905 or other circuitrydescribed herein.

With reference now to FIG. 48, shown is a high-level logic flow 4800 ofan operational process. Intensive operation 93 describes obtaining anassociation between data indicating a current health status of a firstindividual and a record designator (e.g. interface module 3513 creatingor updating a specific record 3831 associating one or more patienthealth status indicators 3842 with one or more record serial numbers,patient names, or other data patterns 3841 that serve to designate thatspecific record 3831) This can occur, for example, in a context in whichuser 3880 is the “first” individual; in which each of the patterns 3841within available tabular data 3820 uniquely identifies a correspondingone of the records 3831-3834; in which some or all of the statusindicators 3842 include a test result 2315, image 2578, datadistillation 2980 (diagnosis 3867, computed negative indication 2989 ofregimen compliance, evaluation, or patient category 3868 assigned orentered by a physician or other care provider 2783, e.g.), or otherhealth status indication 3870 that is “current” (at most about a weekold and not superseded by a newer item of the same type, e.g.); and inwhich one or more such records 3831-3834 may also include medicalhistory data 3843 (non-current indicia, e.g.) pertaining to the firstindividual. This can occur, for example, in a context in which interfacemodule 3513 comprises a telephone menu or website (accessed using ahandheld interface 1002, e.g.) via which one or more other users 3780(caregivers, e.g.) may provide various information as described herein(with reference to media of FIGS. 21-26, e.g.) that interface module3513 then stores as tabular data 3820 (on a network server, e.g.)indexed by respective designation patterns 3841.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for managing the accounting for a hospital or other medicalprovider as described herein without undue experimentation. See, e.g.,U.S. Pat. No. 8,065,162 (“Provider data management and claims editingand settlement system”); U.S. Pat. No. 7,962,350 (“Payment of healthcare insurance claims using short-term loans”); U.S. Pat. No. 7,860,732(“Medicare pharmacy calculator II”); U.S. Pat. No. 7,827,234 (“Privacyentitlement protocols for secure data exchange, collection, monitoringand/or alerting”); U.S. Pat. No. 7,805,318 (“Using a non-profitorganization to satisfy medicare out-of-pocket/troop and productreplacement”); U.S. Pat. No. 7,464,043 (“Computerized method and systemfor obtaining, storing and accessing medical records”); U.S. Pat. No.7,433,827 (“System and method for displaying a health status ofhospitalized patients”); U.S. Pat. No. 7,263,493 (“Delivering electronicversions of supporting documents associated with an insurance claim”);U.S. Pat. No. 6,655,545 (“Medical code system”); and U.S. Pat. No.6,000,828 (“Method of improving drug treatment”).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for retrieving data based on a medical condition as describedherein without undue experimentation. See, e.g., U.S. Pat. No. 7,844,470(“Treatment order processing system suitable for pharmacy and otheruse”); U.S. Pat. No. 7,739,126 (“Method, system, and computer programproduct for physician efficiency measurement and patient health riskstratification”); U.S. Pat. No. 7,707,047 (“Method and system forgenerating personal/individual health records”); U.S. Pat. No. 7,664,659(“Displaying clinical predicted length of stay of patients for workloadbalancing in a healthcare environment”); U.S. Pat. No. 7,640,175(“Method for high-risk member identification”); U.S. Pat. No. 7,624,027(“Method and system for automated medical records processing”); U.S.Pat. No. 7,613,620 (“Physician to patient network system for real-timeelectronic communications and transfer of patient health information”);U.S. Pat. No. 7,444,291 (“System and method for modeling of healthcareutilization”); and U.S. Pat. No. 6,266,645 (“Risk adjustment tools foranalyzing patient electronic discharge records”).

Extensive operation 55 describes causing a wearable article at a firstcare facility to include the data indicating the current health statusof the first individual as an automatic and conditional response tolocal input at the first care facility matching the record designator(e.g. triggering module 3554 transmitting a status-indicative wirelesssignal 2563 to data-handling device 3805 if and only if a detectionmodule 3746 detects one or more recognizable patterns 3841 of user input2473 from user 3880). This can occur, for example, in a context in whichone or more interface modules 3513 in nursing home 3802 include or areoperably coupled with detection module 3746; in which detection module3746 is configured to determine whether or not user input 2473(auditory, optical, keyed, or other data entered by a user, e.g.)includes any instances of a pattern 3841 designating one of the activerecords 3831-3834 of available tabular data 3820; in which data-handlingdevice 3805 is configured to store any status indicator 3842 receivedfrom triggering module 3554; and in which status-indicativecustomization of wearable articles would otherwise incur unnecessarydelay or user participation. In some contexts, such devices may beconfigured to be activated by coming into contact with (the skin of)user 3880 and to detect whether it has ever been removed sinceactivation. Alternatively or additionally, data-handling device 3805 mayindicate the “current health status” by virtue of a (passive or otherradio frequency or ultrasound) identification tag 3853 (previouslycustomized, e.g.) wirelessly detectable by a data handling device in thesame vicinity (within hallway 3709, e.g.). In some contexts, moreover,invocation module 2795 may be configured to coordinate flow 4800automatically (without further input from any user local to the wearablearticle, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for permitting an identification of a person by a wearablearticle as described herein without undue experimentation. See, e.g.,U.S. Pat. No. 8,068,008 (“Emergency responder credentialing system andmethod”); U.S. Pat. No. 8,049,597 (“Systems and methods for securelymonitoring an individual”); U.S. Pat. No. 8,039,093 (“Method forpreparing tamperproof ID documents”); U.S. Pat. No. 7,988,043 (“Fraudprevention in issuance of identification credentials”); U.S. Pat. No.7,979,286 (“Patient-interactive healthcare management”); U.S. Pat. No.7,975,913 (“Discernment card and a discernment card business systemusing the discernment card”); U.S. Pat. No. 7,481,370 (“Removablepatient identification strap for blood recipient verification”); andU.S. Pat. No. 6,748,687 (“Multi-web business form having moisture proofwristband, identification labels and web joint”).

With reference now to FIG. 39, shown is a system 3900 in which one ormore technologies may be implemented. A pregnant patient 3950 who issmoking in a hallway 3909 (at her home or at a healthcare facility thatis “local” to her, e.g.). Her actions are monitored via a network 3990that comprises one or more agents 3994 (at a remote call center 3995,e.g.) who are authorized to monitor and interact with patient 3950 viaone or more devices (smoke detector 3958 and intercom 3959 respectivelyas shown, e.g.) in her vicinity.

With reference now to FIG. 49, shown is a high-level logic flow 4900 ofan operational process. Intensive operation 81 describes obtaining anindication via a first device local to a first individual that the firstindividual is noncompliant with a first health regimen (e.g. detectionmodule 3741 generating a regimen noncompliance determination 2988 orother negative indication 2989 of compliance with a pregnancy regimen2331). This can occur, for example, in a context in which system 2900implements intercom 3959 or resides in network 3990; in which the“first” device comprises at least one of a smoke detector 3958 orcomputer 2670 or other data-handling device 3705 in the same room withpatient 3950 (in a hallway 3909 or other location 204 associated withpatient 3950, e.g.); and in which the “indication via the first device”is a result 2314 of a cigarette smoke concentration indication 2481exceeding a corresponding threshold 2451 (indicating that someone issmoking in hallway 3909, e.g.) or a cigarette smoke detection frequencyindication 2482 exceeding a corresponding threshold 2452 (correspondingto cigarette smoke being detected via smoke detector 3958 one day perweek, e.g.). Alternatively or additionally, in some variants, one ormore configuration modules 3701-3704, detection modules 3741-3746,computation modules 3771-3774, or authorization modules 3791-3794 mayreside in a smoke detector 3958, intercom 3959, kiosk, or otherstationary device 3760 as described herein. Alternatively oradditionally, pregnancy regimen 2331 may include one or more medicinal,dietary, measurement, reporting, or other health-related regimencomponents with which patient 3950 or her local caregivers (nurses,e.g.) may or may not comply. In some contexts, for example, suchthresholds 2451-2453 or other compliance determinants 2393 may bedefined (via a control unit 2705 operated by a specialty serviceprovider 2710, e.g.) with reference to one or more other indications2483 (relating to the individual and received via a camera 2832 or othersensor 2833 residing in interaction unit 2775, e.g.) specific to aparticular regimen 2331 (as defined by a specialist, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for associating an entity (user or device, e.g.) with anotherentity as described herein without undue experimentation. See, e.g.,U.S. Pat. No. 8,023,485 (“Method, system and device for realizing useridentity association”); U.S. Pat. No. 7,979,585 (“System and method toassociate a private user identity with a public user identity”); U.S.Pat. No. 7,970,660 (“Identifying associations between items andemail-address-based user communities”); U.S. Pat. No. 7,941,505 (“Systemand method for associating a user with a user profile in a computernetwork environment”); U.S. Pat. No. 7,894,812 (“Automatic over-the-airupdating of a preferred roaming list (PRL) in a multi-mode device, basedon an account association between the device and a wireless local areanetwork (WLAN) access point”); U.S. Pat. No. 7,743,099 (“Associatingmultiple visibility profiles with a user of real-time communicationsystem”); U.S. Pat. No. 7,716,378 (“System and method to associate aprivate user identity with a public user identity”); U.S. Pat. No.7,703,691 (“Multiple device and/or user association”); U.S. Pat. No.7,627,577 (“System and method for maintaining an association between adistribution device and a shared end user characteristic”); U.S. Pat.No. 6,473,824 (“Dynamic association of input/output device withapplication programs”).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for generating indications of patient compliance ornoncompliance as described herein without undue experimentation. See,e.g., U.S. Pat. No. 8,032,399 (“Treatment regimen compliance andefficacy with feedback”); U.S. Pat. No. 7,917,377 (“Patient data miningfor automated compliance”); U.S. Pat. No. 7,599,892 (“Method for securediagnostic screening, servicing, treatment, and compliance monitoringfor sleep apnea in truck drivers”); U.S. Pat. No. 7,417,205 (“Medicalitem thermal treatment systems and method of monitoring medical itemsfor compliance with prescribed requirements”); U.S. Pat. No. 6,926,667(“Patient compliance monitor”); U.S. Pat. No. 6,790,668 (“Monitoringpatient compliance and bioavailability of drugs by deproteinizing bodyfluids”); U.S. Pat. No. 6,380,858 (“Systems and methods for monitoringpatient compliance with medication regimens”); U.S. Pat. No. 6,161,095(“Treatment regimen compliance and efficacy with feedback”); U.S. Pat.No. 6,124,136 (“Method of monitoring compliance with methadone treatmentprogram”); and U.S. patent application Ser. No. 13/199,053 (“Systematicdistillation of status data relating to regimen compliance”).

Intensive operation 94 describes obtaining an indication via a seconddevice that a second individual is available to participate in anelectronic intercommunication (e.g. interface module 3511 receiving anindication 2484 via one or more response units 2755, 3605 that one ormore qualified agents 294, 3994 are online). This can occur, forexample, in a context in which such agents can each press a button 2079(on an office phone, e.g.) at their workstations to generate suchavailability indications 2484, 2485 when they start or resume working orwhen they accept a particular work task. In some variants, for example,a work task 2441 becomes available to one or more call center agents294, 3994 as an automatic and conditional response to a negativeindication 2989 of compliance (a current or recent condition 2321signaling a patient's failure to report within a prescribed interval,e.g.) and interface module 3511 assigns the work task 2441 (ofparticipating in the electronic intercommunication, e.g.) in response tothe first-arriving indication 2485 (from whichever of the eligible callcenter agents 294, 3994 signals availability first, e.g.) by invokingcommunication module 3681.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for facilitating the operation of a call center or otherwiseinitiating communications as described herein without undueexperimentation. See, e.g., U.S. Pat. No. 8,069,213 (“Method ofcontrolling access to network resources using information in electronicmail messages”); U.S. Pat. No. 7,860,935 (“Conditional communication”);U.S. Pat. No. 7,783,023 (“Systems and methods for providing unifiedcollaboration systems with conditional communication handling”); U.S.Pat. No. 7,484,048 (“Conditional message delivery to holder of locksrelating to a distributed locking manager”); U.S. Pat. No. 7,042,338(“Alerting a care-provider when an elderly or infirm person in distressfails to acknowledge a periodically recurrent interrogative cue”); U.S.Pat. No. 6,307,937 (“Method and apparatus for an adapter card providingconditional access in a communication system”); and U.S. Pat. No.6,108,709 (“System for sending an e-mail message to a first type ofterminal based upon content thereof and selected conditions andselectively forwarding it to a second type of terminal”).

Extensive operation 59 describes signaling the electronicintercommunication as an automatic and conditional response to theindication via the first device local to the first individual that thefirst individual is noncompliant with the first health regimen and tothe indication via the second device that the second individual isavailable to participate in the electronic intercommunication (e.g.communication module 3681 initiating a telephone call 3431, text chatsession 3432, or other electronic intercommunication 3441 as a real-timeresponse to hybrid indication 2485). This can occur, for example, in acontext in which each such indication 2485 signifies both the firstindividual's apparent noncompliance and the second individual'savailability to participate, at least; in which one or more of theabove-described systems and media (of FIG. 1-13 or 20-38, e.g.) residein network 3990; and in which a timely and selective response to varioustypes of device-detectable regimen noncompliance would not otherwise becost-effective. In some contexts in which an initial negative indication2989 of compliance comes from a vessel 2890 containing medication (nothaving been used on schedule, e.g.), for example, incentive acceptancemodule 2820 may transmit a signal 2816 that indicates one or moreincentives 2811, 2812 with the negative indication 2989 of compliance.Such incentives 2811 may include a flat fee or per-minute fee forparticipating in the electronic intercommunication, for example, whichincentives are implemented as another automatic and conditional responseto a hybrid indication 2485 (generally signifying the first individual'sapparent noncompliance and the second individual's availability toparticipate, e.g.). In some contexts, moreover, invocation module 2795may be configured to coordinate flow 4900 automatically (activatingintercom 3959 without further input from call center 3995 or from anyuser local to patient 3950, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for implementing a conditional message as described hereinwithout undue experimentation. See, e.g., U.S. Pat. No. 7,932,837(“Conditional aircraft cabin warning and signalling system fordetermining the cabin status”); U.S. Pat. No. 7,002,454 (“System andmethod for warning an operator of a vehicle if the vehicle is operatingin a condition that may result in drive belt failure”); U.S. Pat. No.6,452,487 (“System and method for warning of a tip over condition in atractor trailer or tanker”); U.S. Pat. No. 6,437,707 (“Detecting a lowperformance takeoff condition for aircraft for use with ground proximitywarning systems”); U.S. Pat. No. 6,373,392 (“Alert device for providinga warning of a baby's condition which may lead to the onset of SIDS”);U.S. Pat. No. 6,310,556 (“Apparatus and method for detecting alow-battery power condition and generating a user perceptible warning”);U.S. Pat. No. 6,310,554 (“Severe weather detection apparatus and methodof detecting and warning of severe weather conditions”); and U.S. Pat.No. 6,211,791 (“Warning system for excessive apparent temperatureconditions”).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for implementing a device-initiated phone call or otheraudible notification as described herein without undue experimentation.See, e.g., U.S. Pat. No. 8,041,017 (“Emergency call service withautomatic third party notification and/or bridging”); U.S. Pat. No.7,650,811 (“Shifting device”); U.S. Pat. No. 7,508,298 (“Automatic crashnotification using prerecorded messages”); U.S. Pat. No. 7,493,281(“Automatic notification of irregular activity”); U.S. Pat. No.7,469,155 (“Handheld communications device with automatic alert modeselection”); U.S. Pat. No. 7,181,192 (“Handheld portable automaticemergency alert system and method”); U.S. Pat. No. 7,076,235 (“Automaticnotification of personal emergency contacts from a wirelesscommunications device”); U.S. Pat. No. 6,442,485 (“Method and apparatusfor an automatic vehicle location, collision notification, and syntheticvoice”); and U.S. Pat. No. 6,112,074 (“Radio communication system withautomatic geographic event notification”).

With reference now to FIG. 40, shown is another example of a system 4000in which one or more technologies may be implemented. One or moretracking units 4020 (implemented in device 305 or near a healthcarerecipient, e.g.) is configured to implement a health-related regimen2331-2339 comprising one or more medicinal components 4011, measurementcomponents 4012, omission components 4013, exercise components 4014, orother regimen components 4015, 4016. In some variants, such tracking mayresult in one or more conditional notifications 4071, 4072 orperformance metrics 4081, 4082 being generated (via localevent-sequencing logic in tracking unit 4020 or medical deviceconfiguration logic 3305 in network 4090, e.g.) as described below.

With reference now to FIG. 50, shown is a high-level logic flow 5000 ofan operational process. Intensive operation 86 describes obtaining via afirst device a scalar indication of how well a first health regimen hasbeen followed by a first individual (e.g. interface module 3512receiving via tracking unit 4020 a percentage or other quantifiedindication 2343 of how well patient 3950 has complied with pregnancyregimen 2331). This can occur, for example, in a context in whichpatient 3950 is the “first” patient; in which smoke detector 3958 andinteraction unit 3505 are each instances of the “first” device; in whichan obstetrician has defined required and suggested parameters forrespective components of pregnancy regimen 2331; in which one or moretracking units 4020 on or near patient 3950 are configured (by aprogrammer or other technician 2761, e.g.) to derive such quantifiedindications 2343 (positively or negatively indicative of compliance,e.g.) from sensor data local to patient 3950 or from user input 2473,and in which the pregnancy regimen 2331 includes one or more omissioncomponents 4013 (not smoking, e.g.). In some contexts, for example,quantified indication 2343 may include an occurrence count (of detectedregimen violations, e.g.), a rate (of calories consumed per day or ofintercommunications or other events required by a reporting regimencomponent, e.g.), or a concentration (of detected metabolites indicativeof compliance or noncompliance as measured by sample tester 3060, e.g.).In some variants, two or more such quantified indications 2343, 2344 mayrespectively reflect the performance by a patient 3950 and her provider(caregiver 991, e.g.) in regard to their respective regimens 2331, 2339or regimen components.

In light of teachings herein, numerous existing techniques may beapplied for applying various provider-specified criteria (relating tocounts or dosages or other quantifications provided by a physician orother service provider, e.g.) to device-detectable health-indicativedata (for determining success, eligibility, or some other thresholdevent, e.g.) as described herein without undue experimentation. See,e.g., U.S. Pat. No. 7,488,291 (“Methods for detecting and monitoringsleep disordered breathing using an implantable medical device”); U.S.Pat. No. 7,487,774 (“Adaptive patient trigger threshold detection”);U.S. Pat. No. 7,465,551 (“Method of determining cytokine dosage forimproving myelosuppressive state”); U.S. Pat. No. 7,366,571(“Neurostimulator with activation based on changes in bodytemperature”); U.S. Pat. No. 7,246,619 (“Snore detecting method andapparatus”); U.S. Pat. No. 7,223,246 (“Diagnosis of the presence ofcochlear hydrops using observed auditory brainstem responses”); U.S.Pat. No. 7,177,684 (“Activity monitor and six-minute walk test fordepression and CHF patients”); U.S. Pat. No. 7,132,238 (“Method ofdetermining a chemotherapeutic regimen based on ERCC1 expression”); U.S.Pat. No. 7,107,095 (“Device for and method of rapid noninvasivemeasurement of parameters of diastolic function of left ventricle andautomated evaluation of the measured profile of left ventricularfunction at rest and with exercise”); U.S. Pat. No. 7,054,688 (“Heartstimulator with evoked response detector and an arrangement fordetermining the stimulation threshold”); U.S. Pat. No. 7,047,083(“Method and apparatus for identifying lead-related conditions usinglead impedance measurements”); U.S. Pat. No. 6,988,498 (“Administrationof CPAP treatment pressure in presence of apnea”); U.S. Pat. No.6,978,177 (“Method and apparatus for using atrial discriminationalgorithms to determine optimal pacing therapy and therapy timing”);U.S. Pat. No. 6,671,548 (“Implantable stimulation device and method fordiscrimination atrial and ventricular arrhythmias”); U.S. Pat. No.6,336,048 (“Implantable active medical device enslaved to at least onephysiological parameter”).

Intensive operation 97 describes obtaining via a second device a scalarindication of how well a second health regimen has been followed by asecond individual (e.g. input module 3625 receiving via device 1242 anevent count or other indication 2346 quantitatively describing how wellpatient 1292 has complied with a personalized regimen 2332 having anexercise component 4014). This can occur, for example, in a context inwhich an accelerometer aboard device 1242 generates indication 2346 as acount of how many steps patient 1292 takes each day. Alternatively oradditionally, in some contexts, a service provider (a programmer orother technician 2761, e.g.) may define required and suggestedparameters for respective regimen components of a personalized regimen2332 and configure one or more tracking units 4020 (comprising device1242, e.g.) to derive such compliance-related quantified indications2346 (event counts or time intervals or measurements, e.g.). In acontext in which regimen 2332 includes an omission component 4013relating to alcohol consumption, for example, such tracking units 4020may include a breathalyzer. Alternatively or additionally, regimen 2332may require a regimen component 4016 of daily reporting (implemented asa conditional notification 4071 or other data upload from a portabletracking unit 4020, e.g.).

Extensive operation 49 describes characterizing a performance of a thirdindividual with a scalar evaluation obtained by mathematically combiningthe scalar indication of how well the first health regimen has beenfollowed by the first individual with the scalar indication of how wellthe second health regimen has been followed by the second individual(e.g. computation module 3771 generating a median performance metric4081 across two or more scalar indications 2343-2349 of regimencompliance performance by or on behalf of patients 250, 1292, 3950 in agiven patient category). This can occur, for example, in a context inwhich the patient category is defined as whichever patients (in aparticular service zone 208 or records archive 820, e.g.) have beenserved repeatedly by a particular provider (a material provider 2781 orcare provider 2783 or corporate entity, e.g.) during the past year; inwhich performance metric 2461 (quantified indication 2343, e.g.)reflects recent behavior of a particular patient 3950 (in relation toregimen 2331, e.g.); in which performance metric 2462 (quantifiedindication 2346, e.g.) reflects recent behavior of patient 1292 (inrelation to regimen 2332, e.g.); in which performance metric 2463reflects recent behavior of patient 250 (in relation to regimen 2332,e.g.); and in which computation module 3771 derives performance metric4081 as the median of these performance metrics 2461-2463. In somecontexts, for example, such component performance metrics 2461-2463express similar respective percentages (negatively indicative ofcompliance, e.g.). Alternatively or additionally, an alternativeperformance metric 4082 may be derived using one or more other componentperformance metrics 2464 relating to other patients 992, 1392 orrelating to other regimen components 4015, 4016 or relating to otherregimens 2333-2338 or components thereof or relating to other periods oftime (a week or a month, e.g.); or other modes of mathematicalcombination (ranking or other common statistical operations, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for calculating and disseminating metrics as described hereinwithout undue experimentation. See, e.g., U.S. Pat. No. 8,078,606(“Rank-based estimate of relevance values”); U.S. Pat. No. 8,069,080(“Methods for generating healthcare provider quality and cost ratingdata”); U.S. Pat. No. 8,065,669 (“Apparatus for automatically convertingnumeric data to a processor efficient format for performing arithmeticoperations”); U.S. Pat. No. 8,046,371 (“Scoring local search resultsbased on location prominence”); U.S. Pat. No. 7,949,643 (“Method andapparatus for rating user generated content in search results”); U.S.Pat. No. 7,865,171 (“Method and system for rating notification”); U.S.Pat. No. 7,826,965 (“Systems and methods for determining a relevancerank for a point of interest”); U.S. Pat. No. 7,730,005 (“Issue trackingsystem using a criteria rating matrix and workflow notification”); U.S.Pat. No. 7,630,913 (“Automated processing of medical data for disabilityrating determinations”); and U.S. Pat. No. 6,832,245 (“System and methodfor analyzing communications of user messages to rank users and contactsbased on message content”).

With reference now to FIG. 41, shown is another example of a system 4100in which one or more technologies may be implemented. A local user 4180and a handheld device 4110 each have a field of view 4150 within whichseveral people 4141, 4142, 4143, 4144 are visible. A portion 4172 of animage 4170 (depicting person 4144, e.g.) shown on a touchscreen 4115 ofthe device 4110 captures a corresponding portion 4152 of the field ofview 4150 so that, in some contexts, user 4180 can designate a patient(person 4144, e.g.) selectively (by touching portion 4172, e.g.). Insome contexts, such designation can trigger closer tracking(supplemental capture of facial image data or other biometric data 2540to facilitate recognition or detection of devices on person 4144, e.g.)or other device-assisted investigation concerning that patient and hermedical status, as described below.

With reference now to FIG. 51, shown is a high-level logic flow 5100 ofan operational process. Intensive operation 82 describes obtaining afield of view within which a specific portion of the field of viewincludes a view of a first patient (e.g. detection module 3744 receivingan image 4170 of which a lower-right portion 4172 depicts the “first”patient). This can occur, for example, in a context in which the firstpatient is person 4144; in which device 4110 is a handheld devicecomprising a camera 2053 via which image 4170 was captured; and in whichdetection module 3744 is configured to distinguish one person 4144 fromanother in (a raw version of) the image 4170. In some variants, forexample, detection module 3744 may reside within device 4110 and beconfigured to highlight image features (with blinking brackets orsimilar visible markings, e.g.) of one or more individuals visiblewithin image 4170 that detection module 3744 identifies (as human facesor figures, e.g.) in an enhanced version of image 4170 (visible to user4180, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for locating symbols, faces, or other shapes in field of viewas described herein without undue experimentation. See, e.g., U.S. Pat.No. 8,295,556 (“Apparatus and method for determining line-of-sightdirection in a face image and controlling camera operations therefrom”);U.S. Pat. No. 8,259,169 (“Eye-gaze detecting device and eye-gazedetecting method”); U.S. Pat. No. 8,188,880 (“Methods and devices foraugmenting a field of view”); U.S. Pat. No. 8,045,805 (“Method fordetermining whether a feature of interest or an anomaly is present in animage”); U.S. Pat. No. 7,986,828 (“People detection in video and imagedata”); U.S. Pat. No. 7,912,288 (“Object detection and recognitionsystem”); U.S. Pat. No. 7,903,880 (“Image processing apparatus andmethod for detecting a feature point in an image”); U.S. Pat. No.7,856,142 (“Methods and systems for detecting character content in adigital image”); U.S. Pat. No. 7,787,692 (“Image processing apparatus,image processing method, shape diagnostic apparatus, shape diagnosticmethod and program”); U.S. Pat. No. 7,715,659 (“Apparatus for and methodof feature extraction for image recognition”); U.S. Pat. No. 7,682,025(“Gaze tracking using multiple images”); U.S. Pat. No. 7,630,544(“System and method for locating a character set in a digital image”);U.S. Pat. No. 7,590,275 (“Method and system for recognizing a candidatecharacter in a captured image”); U.S. Pat. No. 7,572,008 (“Method andinstallation for detecting and following an eye and the gaze directionthereof”); U.S. Pat. No. 7,526,123 (“Estimating facial pose from asparse representation”); U.S. Pat. No. 7,454,067 (“Symbol classificationdepending on cluster shapes in difference image”); U.S. Pat. No.7,403,656 (“Method and apparatus for recognition of character string inscene image”); U.S. Pat. No. 6,700,604 (“Image capturing method andapparatus for determining a shape of an object”).

Intensive operation 88 describes obtaining user input selectivelyindicating the first patient by identifying the specific portion thatdepicts the first patient (e.g. interface module 3516 receiving auditoryor touchscreen input 2472 indicating person 4144 from user 4180 afteroperation 82). This can occur, for example, in a context in which suchinput 2472 includes coordinates 2381, 2382 indicating a position ontouchscreen 4115 within a portion 4172 of image 4170 that was touched byuser 4180; in which user 4180 intends or perceives that such input is“selective” insofar that it indicates less than all of the field of view(image 4170, e.g.); in which the specific portion 4172 depicts only onepatient (person 4144, e.g.); and in which other people depicted in image4170 (if there are any) are therefore not “selectively indicated” bysuch input. In some contexts, for example, ambiguous input (spanning twoor more portions of image 4170 respectively identifying two or morepersons 4143, 4144 depicted therein, e.g.) may not register (may nottrigger interface module 3516 to take any action perceptible to user4180, e.g.) or may cause interface module 3516 to prompt user 4180 tospecify which person user 4180 intends to designate (by asking the userfor a menu selection or by zooming in on part of the image 4170 thatdepicts them to prompt a more precise designation via touchscreen 4115,e.g.). Alternatively or additionally, interface module 3516 may beconfigured to provide (via a speaker or touchscreen 4115 of device 4110,e.g.) one or more unique patient designations 2501, 2502 (patient namesor birthdates or serial numbers retrieved from correspondinginstitutional records 3191-3197, e.g.) by which user 4180 may resolvethat person 4144 has been identified correctly (in a variant in whichinterface module 3516 uses a voice menu confirmation or other protocolfor prompting user 4180 for clarification, e.g.). Alternatively oradditionally, interface module 3516 may be configured to extract suchinstitutional data by a direct detection (via a passive wireless linkage2776 or line of sight, e.g.) of a data-handling device 3805 (aninteraction unit 2775, e.g.) worn by person 4144 (individual 2782,e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for highlighting detected features in displays or other visualmedia as described herein without undue experimentation. See, e.g., U.S.Pat. No. 7,911,482 (“Method and system for efficient annotation ofobject trajectories in image sequences”); U.S. Pat. No. 7,853,586(“Highlighting occurrences of terms in documents or search results”);U.S. Pat. No. 7,639,396 (“Editing of digital images, including (but notlimited to) highlighting and shadowing of image areas”); U.S. Pat. No.7,555,159 (“Image highlight correction using illumination specific HSVcolor coordinate”); U.S. Pat. No. 7,119,814 (“System and method forannotation on a moving image”).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for comparing a face or other informational element with adatabase of similar items as described herein without undueexperimentation. See, e.g., U.S. Pat. No. 8,000,528 (“Method andapparatus for authenticating printed documents using multi-level imagecomparison based on document characteristics”); U.S. Pat. No. 7,949,191(“Method and system for searching for information on a network inresponse to an image query sent by a user from a mobile communicationsdevice”); U.S. Pat. No. 7,908,518 (“Method, system and computer programproduct for failure analysis implementing automated comparison ofmultiple reference models”); U.S. Pat. No. 7,856,137 (“Apparatus andmethod for verifying image by comparison with template image”); U.S.Pat. No. 7,831,559 (“Concept-based trends and exceptions tracking”);U.S. Pat. No. 7,787,693 (“Text detection on mobile communicationsdevices”); U.S. Pat. No. 7,644,055 (“Rule-based database object matchingwith comparison certainty”); U.S. Pat. No. 7,443,787 (“Cluster system,cluster member, and failure recovery method and program thereof”); U.S.Pat. No. 6,424,729 (“Optical fingerprint security verification usingseparate target and reference planes and a uniqueness comparisonscheme”); U.S. Pat. No. 6,167,398 (“Information retrieval system andmethod that generates weighted comparison results to analyze the degreeof dissimilarity between a reference corpus and a candidate document”);U.S. Pat. No. 6,134,014 (“Apparatus and method of inspecting phase shiftmasks using comparison of a mask die image to the mask image database”).

Extensive operation 51 describes signaling medical data about the firstpatient as an automatic and conditional response to the user inputselectively indicating the first patient by identifying the specificportion that depicts the first patient (e.g. triggering module 3552automatically causing medical history data 3843 pertaining to person4144 to be transmitted if and only if interface module 3516 successfullyobtains input 2472 as described above). This can occur, for example, ina context in which one or more interface modules 3511-3516 are operablycoupled to triggering modules 3551-3556 as described herein; in whichrecord 3834 pertains specifically to person 4144; and in which othertabular data 3820 from the same source is not accessible to triggeringmodule 3552. In some contexts, for example, such input 2472 comprises apattern 3841 uniquely designating such record 3834. Alternatively oradditionally, triggering module 3552 may trigger an acquisition orretrieval of one or more status indicators 3842 (current images 2575,measurements, regimens 2335, query responses 2459, or unfilled medicalorders 2511, e.g.) pertaining to person 4144 (via a data-handling device3805 worn by person 4144, e.g.). This can occur, for example, in acontext in which device 4110 resides in networks 2790, 3590 andimplements interaction unit 3505; and in which a healthcare provider(user 4180, e.g.) could not otherwise manage a crowded environment(numerous patients in a clinic or office or cafeteria, e.g.)effectively. In some contexts, moreover, invocation module 2795 may beconfigured to coordinate flow 5100 automatically (without further inputfrom any user local to the first patient, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for extracting an indication that a patient (mammal, e.g.) wastreated for a particular condition as described herein without undueexperimentation. See, e.g., U.S. Pat. No. 8,073,711 (“Method and systemfor obtaining health-related records and documents using an onlinelocation”); U.S. Pat. No. 8,065,347 (“Managing protocol amendments inelectronically recorded clinical trials”); U.S. Pat. No. 7,972,274(“System and method for analyzing a patient status for congestive heartfailure for use in automated patient care”); U.S. Pat. No. 7,935,055(“System and method of measuring disease severity of a patient before,during and after treatment”); U.S. Pat. No. 7,899,764 (“Medicalontologies for machine learning and decision support”); U.S. Pat. No.7,552,039 (“Method for sample processing and integrated reporting of doghealth diagnosis”); U.S. Pat. No. 7,533,353 (“Electronic system forcollecting and automatically populating clinical order information in anacute care setting”); and U.S. Pat. No. 7,069,085 (“Method and apparatusto produce, maintain and report information related to patient treatmentusing medical devices”).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for annotating an electronic record as described hereinwithout undue experimentation. See, e.g., U.S. Pat. No. 7,941,009(“Real-time computerized annotation of pictures”); U.S. Pat. No.7,913,162 (“System and method for collaborative annotation using adigital pen”); U.S. Pat. No. 7,847,970 (“System and method for receptionanalysis and annotation of prescription data”); U.S. Pat. No. 7,546,524(“Electronic input device system and method using human-comprehensiblecontent to automatically correlate an annotation of a paper documentwith a digital version of the document”); U.S. Pat. No. 7,373,342(“Including annotation data with disparate relational data”); U.S. Pat.No. 7,286,894 (“Hand-held computer device and method for interactivedata acquisition analysis annotation and calibration”); U.S. Pat. No.7,269,787 (“Multi-document context aware annotation system”); U.S. Pat.No. 7,263,493 (“Delivering electronic versions of supporting documentsassociated with an insurance claim”); U.S. Pat. No. 6,839,403(“Generation and distribution of annotation overlays of digital X-rayimages for security systems”); U.S. Pat. No. 6,721,921 (“Method andsystem for annotating documents using an independent annotationrepository”); U.S. Pat. No. 6,594,519 (“Distributed real timecatalog-based annotation and documentation system for cardiologyprocedures”); U.S. Pat. No. 6,575,901 (“Distributed real timereplication-based annotation and documentation system for cardiologyprocedures”); U.S. Pat. No. 6,397,181 (“Method and apparatus for voiceannotation and retrieval of multimedia data”).

With reference now to FIG. 42, shown is another example of a system 4200in which one or more technologies may be implemented in one or moredevices 305 (in a vicinity of patient 4250, e.g.) having a wirelesslinkage 4294 with network 4290. In some variants one or more regimennoncompliance indications 4271, 4272 relating to patient 4250 triggerconditional or other incentive indications 4281, 4282 being communicated(via a display 2426, 4226 of a vehicle 4243 or glasses or other wearablearticle 4245, e.g.) to patient 4250 (via, e.g.). See FIG. 52.Alternatively or additionally one or more such devices may comprise oneor more elements 4232 (in a respective portion 2581, 4231 of one or moreimages 2580, 4230 each implementing a countdown timer 2310, e.g.) toindicate a remaining portion (7 minutes and 54 seconds, e.g.) of one ormore time intervals 2543, 2544 associated with respective tasks(starting an intercommunication or arriving at a location, e.g.). SeeFIG. 57.

With reference now to FIG. 52, shown is a high-level logic flow 5200 ofan operational process. Intensive operation 89 describes obtaining anindication whether or not a first individual is compliant with a firsthealth regimen (e.g. input module 3624 failing to receive an indication2349 that patient 4250 took a medication or measurement within a timeinterval 2545 required by a component 4015 of his therapeutic regimen2336). This can occur, for example, in a context in which a medicinalcomponent 4011 or measurement component 4012 required that suchmedication or measurement be administered daily; in which anothercomponent 4015 of regimen 2336 required that the indication 2349 of suchadministration (from an administration detection module 2848 or anadministration detection feature 2880 directly or indirectly coupledwith input module 3624, e.g.) be received within a prescribed timeinterval (between 11 am and 1 pm, e.g.) each day; in which theeffectiveness of regimen 2336 depends heavily upon such timelyadministration; and in which such indication 2349 was not received orwas received early or late today. In some contexts, for example, suchreporting may be implemented via a wearable device (headset 4244, e.g.)or other device associated with patient 4250.

Intensive operation 96 describes responding to the indication whether ornot the first individual is compliant with the first health regimen bycausing a device associated with the first individual to receive anindication of an artificial incentive (e.g. triggering module 3551responding to the absence of the indication 2349 by causing a wearablearticle 4245 or other device associated with patient 4250 to receive anindication 2553 of a particular payment in kind 2618 or other benefit2620 available to patient 4250 or to another recipient 2722 in exchangefor participating in a one-minute telephone call 3431 or similarelectronic intercommunication 3443). This can occur, for example, in acontext in which patient 4250 and his care provider 2783 are busy people(prone to exhibit imperfect compliance and intermittent followthroughand availability, e.g.); in which triggering module 3551 associatespatient 4250 with one or more wearable articles 4245 (headsets 4244,e.g.) or handhelds 2074 or vehicles 4243 operable for communicating thebenefit 2620; and in which such benefit 2620 is not large enough tomotivate regimen noncompliance but is generally large enough to motivatethe patient 4250 to participate in such a dialog 3433. Alternatively oradditionally, triggering module 3551 may be configured to associate hiscare provider 2783 or another recipient 2722 with a delivery unit 2725operable for communicating another incentive 2640 (penalty for failingto participate in the dialog 3433, e.g.). In some contexts, for example,a wearable article associated with patient 4250 (headset 4244, e.g.) ora data-handling device 3705 associated with another recipient 2722 inhis household, e.g.) may be configured to announce “please be advisedthat your home's cable television service will be turned off if [patientX] does not call Dr. Smith's office before 2 pm” (via speaker 3509,e.g.) or to sound a reward-indicative ringtone (a cash register“ching-ching” sound, e.g.) signaling that answering the call willtrigger a lottery eligibility 2646 or other positive incentive 2640.This can occur, for example, in a context in which such messagerecipients have configured such ringtones on their own devices or areotherwise aware of what such ringtones signify; in which such personshave cognitive or other behavioral attributes that make independenttimely compliance uncertain; in which adequately ensuring compliancewith regimen 2336 would otherwise require that patient 4250 behospitalized; and in which a service provider 2710 (insurer, e.g.)designs such artificial incentives and timely notifications (comprisingregimen 2336, e.g.) as a cost-effective alternative to hospitalization.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for motivating or monitoring voluntary participation ininformation management protocols as described herein without undueexperimentation. See, e.g., U.S. Pat. No. 8,056,118 (“Systems andmethods for universal enhanced log-in, identity document verification,and dedicated survey participation”); U.S. Pat. No. 7,828,554 (“Systemfor delivering an educational program to a remote site and formonitoring participation therein”); U.S. Pat. No. 6,807,532 (“Method ofsoliciting a user to input survey data at an electronic commerceterminal”); and U.S. patent application Ser. No. 13/066,442(“Cost-effective resource apportionment technologies suitable forfacilitating therapies”).

Extensive operation 53 describes signaling a decision whether or not tomanifest the artificial incentive after the device associated with thefirst individual receives the indication of the artificial incentive andresponsive to an indication whether or not a dialog occurs between thefirst individual and a second individual (e.g. authorization module 3792placing an electronic order 2512 as an automatic and conditionalresponse to an indication 2487 from caregiver 1391 that patient 4250 didnot call her office by 2 pm today, the electronic order 2512 directingthat cable television service for home 289 be turned off). This canoccur, for example, in a context in which patient 4250 lives in home289; in which service provider 2710 pays for the cable televisionservice for home 289; in which caregiver 1391 is the “second” individual(Dr. Smith or her assistant, e.g.); in which triggering module 3551responds to the absence of the indication 2349 of compliance bytransmitting a message 2290 to caregiver 1391 (via an email or other appresident on device 1342, e.g.) asking whether patient 4250 called Dr.Smith's office by 2 pm; and in which Dr. Smith is motivated to receivethe call and to respond truthfully and promptly to the message 2290because she understands regimen 2336. In some contexts, moreover,invocation module 2795 may be configured to coordinate flow 5200automatically (without further input from any user local to the firstindividual, e.g.).

In light of teachings herein, also, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for determining whether someone has accepted a telephone callas described herein without undue experimentation. See, e.g., U.S. Pat.No. 7,680,260 (“Detecting a voice mail system answering a call”); U.S.Pat. No. 7,386,101 (“System and method for call answer determination forautomated calling systems”); U.S. Pat. No. 7,260,205 (“Call waitingusing external notification and presence detection”); U.S. Pat. No.6,738,613 (“Telephone set having automatic incoming-call acknowledgementdetection”); U.S. Pat. No. 6,697,456 (“Speech analysis based answerdetection for IP based telephones”); U.S. Pat. No. 6,650,751 (“Answerdetection for IP based telephones using passive detection”); and U.S.Pat. No. 6,111,946 (“Method and system for providing answer supervisionin a switched telephone network”).

With reference now to FIG. 43, shown is another example of a system 4300in which one or more technologies may be implemented. A noncomplianceresponse sequencing unit 4310 (implemented in control unit 2705, e.g.)comprises tabular data 4320 (configured by service provider 2710 ortechnician 2761, e.g.). Two or more event detection modules 4331, 4332,4333, 4334, 4335 (implemented in one or more tracking units 4020 localto one or more patients, e.g.) each respectively correspond to adevice-detectable noncompliance event 4311, 4312, 4313, 4314, 4315relating to one or more regimens 2331-2339 prescribed for saidpatient(s). Tabular data 4320 associates two or more of thesenoncompliance events 4311, 4313, 4315 each with a respective response4301, 4302, 4303 that can be implemented by a respective responseimplementation module 4341, 4342, 4343 (local to one or more patients orproviders, e.g.). See FIG. 53. Response implementation module 4341 willbe triggered in response to a noncompliance event 4311 being detected(irrespective of other events 4313-4315 being detected or not, e.g.),for example, whereas response implementation module 4343 will betriggered only if several noncompliance events 4311, 4313, 4315 aredetected.

With reference now to FIG. 53, shown is a high-level logic flow 5300 ofan operational process. Intensive operation 85 describes obtaining afirst indication whether or not a first patient has violated a firsthealth regimen (e.g. input module 3626 receiving an indication 2555 thatthe “first” patient has failed to complete a particular task 2442required by regimen 2337 within an allowable time period). This canoccur, for example, in a context in which regimen 2337 is designed toaddress a serious eating disorder (anorexia nervosa, e.g.) for which thefirst patient 250 has been admitted (by hospital 202, e.g.); in whichthe failure to complete task 2442 has been recognized (asnoncompliance-indicative event 4311, e.g.) by an event detection module4331 that transmits the “first” indication 2555; and in which system4300 resides in network 290. In some contexts, for example, task 2442may include the first patient ordering breakfast every morning by 10 am.Alternatively or additionally, triggering module 3556 may be configuredto generate an order 2513 (requesting that the first patient be weighedevery day, e.g.) as an automatic and conditional response to one or moresuch noncompliance-indicative events 4311, 4312 being signaled to inputmodule 3626.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for selecting and applying thresholds or other criteria asdescribed herein without undue experimentation. See, e.g., U.S. Pat. No.8,069,236 (“Flow control of events based on threshold, grace period, andevent signature”); U.S. Pat. No. 8,061,592 (“Overdraft thresholdanalysis and decisioning”); U.S. Pat. No. 8,005,685 (“Ranking air travelsearch results based upon user criteria”); U.S. Pat. No. 7,976,171(“Projector cooling system with time dependent temperature threshold”);U.S. Pat. No. 7,898,995 (“Dynamic adjustment of inactivity timerthreshold for call control transactions”); U.S. Pat. No. 7,894,448(“Proving that a user profile satisfies selection criteria for targeteddata delivery”); U.S. Pat. No. 7,849,398 (“Decision criteria forautomated form population”); U.S. Pat. No. 7,742,193 (“Method forinspecting prints identifying differences exceeding a threshold”); U.S.Pat. No. 7,624,447 (“Using threshold lists for worm detection”); U.S.Pat. No. 7,592,859 (“Apparatus to compare an input voltage with athreshold voltage”); and U.S. Pat. No. 7,536,301 (“System and method forimplementing real-time adaptive threshold triggering in acousticdetection systems”).

Intensive operation 90 describes obtaining a second indication whetheror not the first patient has violated the first health regimen (e.g.input module 3627 receiving an indication 2556 that the first patienthas not complied with an omission component 4013 of regimen 2337). Thiscan occur, for example, in a context in which regimen 2337 prohibitscertain behaviors comprising at least one noncompliance-indicative event4315 reported to have occurred via an event detection module 4335(implemented in a questionnaire app completed by one or more careproviders 2783, e.g.) that transmits indication 2556. In some contexts,for example, such behaviors may include inducing vomiting or failing tomaintain a body weight above a particular threshold 2456 (5% below aweight of patient 250 measured upon admission to hospital 202, e.g.).

Extensive operation 52 describes signaling a decision whether or not toinitiate an electronic communication between the first patient and aprovider as an automatic and conditional response to the firstindication whether or not the first patient has violated the firsthealth regimen but not to the second indication whether or not the firstpatient has violated the first health regimen (e.g. triggering module3553 transmitting an order 2514 to agent 294 as an automatic response4301 to one or more noncompliance-indicative events 4311 received fromevent detection module 4331). This can occur, for example, in a contextin which a work order 2514 calls for agent 294 to send a therapeuticmessage 2290 (advice or encouragement in a periodic email or textmessage to patient 250, e.g.) or to conduct telephonic counseling withpatient 250; in which triggering module 3553 initiates such therapeuticresponses as a direct response to an indication 2555 of minornoncompliance received via input module 3626 and without regard to anyother noncompliance indications 2556 (or lack thereof) received viainput module 3627. (It should be noted that, for semantic reasonsrelating to antecedent basis, flow 5300 is not presented in a mostlikely sequence of occurrence: more typically operation 52 will precedeor overlap operation 90.)

Extensive operation 56 describes signaling a decision whether or not toroute the provider to the first patient as a conditional response to thefirst indication whether or not the first patient has violated the firsthealth regimen and to the second indication whether or not the firstpatient has violated the first health regimen (e.g. authorization module3791 implementing a recommended response 4303 of placing an order 2515or request that caregiver 1391 visit patient 250 every other day if twoparticular conditions 2326, 2327 are present and otherwise nottransmitting any such order or request). This can occur, for example, ina context in which regimen 2337 includes such response 4303 as aconditional response to such conditions; in which “the provider” is acorporation that employs agent 294 and caregiver 1391; in whichcondition 2327 (manifested as a voltage level of a particular electricalnode 3487, e.g.) comprises a particular indication 2555 (of a “minor”noncompliance-indicative event 4311, e.g.) received via input module3626; in which condition 2326 (manifested as a voltage level of one ormore other electrical nodes 3488, e.g.) comprises another particularindication 2556 (of a “major” noncompliance-indicative event 4315, e.g.)received via input module 3627; and in which a measured response tominor or moderate instances of regimen noncompliance would not otherwiseoccur. In some contexts, for example, regimen 2337 may include anintermediate programmatic response 4302 of an extra telephonic orin-person visit scheduled (as another instance of operation 52 or 56,e.g.) in response to an indication 2554 of an intermediatenoncompliance-indicative event 4313 (a physician's notation or utterancerecognized by event detection module 4333 of patient 250 exercising toexcess or consuming over-the-counter laxatives, e.g.). In some contexts“the provider” may comprise a single individual (caregiver 1391, e.g.)who can participate in the electronic communication and also be routedto patient 250 (at home 289 or a room in hospital 202, e.g.)respectively pursuant to operations 52 and 56. In some variants,moreover, authorization module 3791 may be configured to “route theprovider to the first patient” by generating a task list 2445 or map2423 (from which caregiver 1391 may conduct her work, e.g.) thatdesignates a location of a home 289 or hospital room (including aresidential address or room number, e.g.) at which patient 250 isresiding. In some contexts, moreover, invocation module 2795 may beconfigured to coordinate flow 5300 automatically (without further inputfrom any user via network 4390, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for routing an entity as described herein without undueexperimentation. See, e.g., U.S. Pat. No. 8,290,701 (“Vehicle routeselection based on energy usage”); U.S. Pat. No. 8,255,147 (“Air trafficcontrol”); U.S. Pat. No. 8,155,811 (“System and method for optimizing apath for a marine vessel through a waterway”); U.S. Pat. No. 8,140,592(“Delivery operations information system with route adjustment featureand methods of use”); U.S. Pat. No. 8,027,784 (“Personal GPS navigationdevice”); U.S. Pat. No. 8,005,488 (“Automatic service vehicle hailingand dispatch system and method”); U.S. Pat. No. 8,000,892 (“Pedestrianmapping system”); U.S. Pat. No. 7,693,653 (“Vehicle routing and pathplanning”); U.S. Pat. No. 7,653,457 (“Method and system for efficientpackage delivery and storage”); U.S. Pat. No. 7,587,369 (“Trusted andsecure techniques, systems and methods for item delivery andexecution”); and U.S. Pat. No. 7,487,114 (“System and method forassociating aerial images, map features, and information”).

With reference now to FIG. 44, shown is another example of a system 4400in which one or more technologies may be implemented. A data-handlingunit 4430 interacts with an automated teller machine (ATM) 4410 via oneor more linkages 4494 and network 4490. Data-handling unit 4430(residing in control unit 2705, e.g.) may handle one or more admissionindications 4421, 4422 (relating to a hospital or other institutionhaving admitted a patient or not, e.g.); readmission indications 4431,4432 (relating to the patient having been readmitted or not, e.g.); ortransfer authorizations 4435 (relating to an item or other incentivethat may be dispensed to the patient or not, e.g.). In some contexts,ATM 4410 may interact with a patient 4450 who is in a field of view of acamera 4442 and is operating a passenger vehicle 4443, as describedbelow.

With reference now to FIG. 54, shown is a high-level logic flow 5400 ofan operational process. Intensive operation 84 describes assigning acomponent of an artificial incentive to a first patient partly based onan indication that the first patient has been admitted to a firstinstitution in relation to a particular condition and partly based on anindication that the first patient has not undergone an institutionalreadmission (e.g. selection module 3533 assigning a daily cash allowanceor similar tangible benefit 2620 to patient 4450 only if both conditionsare met). This can occur, for example, in a context in which the “first”institution is a psychiatric hospital; in which the particular conditioncomprises a pathology (clinical depression, e.g.); in which datadistillation module 3422 generates one or more admission indications4421, 4422 (from a search result comprising record 3191, e.g.) thatpatient 4450 has been admitted to the psychiatric hospital in relationto the particular condition; in which data distillation module 3422likewise generates a readmission indication 4431 (from a search resultcomprising record 3192, e.g.) that patient 4450 has not since beenadmitted to any known hospital or a readmission indication 4432 (from asearch result comprising record 3193, e.g.) that patient 4450 has notsince been admitted to any participating regional hospital for any“avoidable” medical treatment related to the particular condition (adrug overdose or wound apparently inflicted by the patient 4450, e.g.);and in which search bot 3421 refreshes such records regularly (hourly ordaily, e.g.) by searching all records of a network of regional hospitalsnear ATM 4410 (using one or more identifiers of patient 4450, e.g.). Insome contexts, for example, selection module 3533 may perform operation84 by designating a $20 cash credit (in lieu of a service 2648 or otheravailable incentive 2640, e.g.) for patient 4450 whenever bothconditions are met. Alternatively or additionally, selection module 3533may be configurable (by a caregiver or patient 4450 having access tointeraction unit 3505, e.g.) so that such conditions will result in adesignation of an alternative incentive component (a payment in kind2618, e.g.). In some variants, moreover, such assignment may becontingent upon a patient's location (visiting an ATM or caregiver 991,e.g.) or upon one or more other determinants 2393 (fulfillment of one ormore medicinal components 4011, measurement components 4012, or otherregimen components 4016 described herein, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for establishing which patients have been admitted and treatedfor a particular condition as described herein without undueexperimentation. See, e.g., U.S. Pat. No. 7,996,074 (“System and methodfor providing closely-followed cardiac therapy management throughautomated patient care”); U.S. Pat. No. 7,991,485 (“System and methodfor obtaining, processing and evaluating patient information fordiagnosing disease and selecting treatment”); U.S. Pat. No. 7,942,817(“Patient monitoring and treatment medical signal interface system”);U.S. Pat. No. 7,827,043 (“Method using a global server for providingpatient medical histories to assist in the delivery of emergency medicalservices”); U.S. Pat. No. 7,698,154 (“Patient-controlled automatedmedical record, diagnosis, and treatment system and method”); U.S. Pat.No. 7,395,216 (“Using predictive models to continuously update atreatment plan for a patient in a health care location”); U.S. Pat. No.7,395,214 (“Apparatus, device and method for prescribing, administeringand monitoring a treatment regimen for a patient”); U.S. Pat. No.7,204,805 (“Patient conditional diagnosis, assessment and symptomtracking system”); U.S. Pat. No. 7,069,085 (“Method and apparatus toproduce, maintain and report information related to patient treatmentusing medical devices”); U.S. Pat. No. 6,726,634 (“System and method fordetermining a condition of a patient”); U.S. Pat. No. 6,405,165(“Medical workstation for treating a patient with a voice recordingarrangement for preparing a physician's report during treatment”); andU.S. Pat. No. 6,338,039 (“Method for automated collection ofpsychotherapy patient information and generating reports and treatmentplans”).

Extensive operation 57 describes transmitting to the first patient aresult of assigning the component of the artificial incentive to thefirst patient partly based on the indication that the first patient hasbeen admitted to the first institution in relation to the particularcondition and partly based on the indication that the first patient hasnot undergone the institutional readmission (e.g. authorization module3793 transmitting a transfer authorization 4435 to ATM 4410 so that anyof the above-referenced $20 cash credits assigned by selection module3533 will automatically be dispensed whenever patient 4450 transactsbusiness at a qualifying ATM 4410 until and unless patient 4450undergoes an institutional readmission deemed “avoidable” by serviceprovider 2710). This can occur, for example, in a context primary unit3405 and interaction unit 3505 are operably coupled to a computer 2670or other data-handling device 3705 (implemented in network 4490, e.g.);in which the result 2311 of the assignment includes a dispensationtrigger 2304 being transmitted to ATM 4410 (implementing the transferauthorization 4435 as an immediate cash dispensation, e.g.); in whichservice provider 2710 is an auditor (having authority to implement aclawback or other payment reduction under applicable state laws orMedicare regulations or policies internal to an accountable careorganization, e.g.) or agent 2762 thereof; and in which anyinstitutional readmissions being thus categorized as “avoidable” wouldotherwise be much more costly for a provider (of health insurance orcare, e.g.) to address. Alternatively or additionally, one or more othertransfer authorizations 4435 (authorizing a transfer of points 2616,credits 2617, payments in kind 2618, or other resources 2619, e.g.) mayaffect event-sequencing structures (in network 4490, e.g.) to implementother benefits 2620 (for one or more readmission indications 4431, 4432being negatively indicative of readmission, e.g.). This can occur, forexample, in a context in which such benefits 2620 are a sufficientincentive 2640 for qualifying patients 4450 (released from a hospital202 and at risk for a much-more-costly hospital readmission, e.g.)generally to maintain a physician-specified home care or othertherapeutic or monitoring regimen 2333 well enough to avoid suchreadmission but in which such benefits are not so large as to causephysician bribes or similar overt corruption to become common. In somecontexts, moreover, invocation module 2795 may be configured tocoordinate flow 5400 automatically (without further input from any userlocal to patient 4450, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for causing a vending machine actuation or other item deliveryas described herein without undue experimentation. See, e.g., U.S. Pat.No. 8,068,933 (“Products and processes for vending a plurality ofproducts via defined groups”); U.S. Pat. No. 8,041,454 (“Automatedbusiness system and method of vending and returning a consumerproduct”); U.S. Pat. No. 8,002,144 (“Drive system for a vending machinedispensing assembly”); U.S. Pat. No. 7,844,363 (“Vending machineapparatus to dispense herbal medications and prescription medicines”);U.S. Pat. No. 7,783,379 (“Automated vending of products containingcontrolled substances”); U.S. Pat. No. 7,753,091 (“Device and method forcontrolling the filling of a cup by a vending machine”); U.S. Pat. No.7,536,360 (“Electronic purchase of goods over a communications networkincluding physical delivery while securing private and personalinformation of the purchasing party”); U.S. Pat. No. 7,272,571 (“Methodand apparatus for effective distribution and delivery of goods orderedon the World-Wide-Web”); U.S. Pat. No. 6,799,165 (“Apparatus and methodsfor inventory, sale, and delivery of digitally transferable goods”); andU.S. Pat. No. 6,536,189 (“Computerized, monitored, temperature affected,delivery system for perishable goods”).

With reference now to FIG. 45, shown is another example of a system 4500in which one or more technologies may be implemented. A wearable orhandheld device 4575 borne by or associated with patient 4550 isconfigured to observe or be observed by a portable device 4540 borne byor associated with a healthcare provider 4560. Portable device 4540 mayinclude one or more (instances of) therapeutic modules 4541 (an inhaler3692 or transfusion bag 3693, e.g.); medical data acquisition modules4542 (sample extraction or measurement or imaging or other diagnosticmedical equipment 2080, e.g.); or other sensors 2833 (configured todetect whether portable device 4540 is in the same room with orotherwise within a particular vicinity 4585 of patient 4550, e.g.). Insome embodiments, one or more primary functions of portable device 4540will remain disabled (by a failsafe or other disablement feature 3365thereof, e.g.) until an order 4538 associates patient 4550 with portabledevice 4540 and until portable device 4540 is in the vicinity 4585 ofpatient 4550. Alternatively or additionally, one or both devices may beoperably coupled (via a wireless linkage 2776, e.g.) with one or morenetworks 2790, 4590 described herein.

With reference now to FIG. 55, shown is a high-level logic flow 5500 ofan operational process. Intensive operation 87 describes obtaining anindication that an order associates a first patient with a medicaldevice (e.g. input module 3628 being operated by a caregiver 991 toupload an order 4538 allocating a portable device 4540 or other medicalequipment 2080 or material to be used for or by patient 4550 to the oneor more networks 2790, 4590). This can occur, for example, in a contextin which the medical device is associated with a therapeutic componentor measurement component 4012 of a particular regimen 2338; in whichresponse unit 3605 resides in system 941 or network 4590; and in whichcaregiver 991 generates the order 4538 by prescribing regimen 2338 topatient 4550. In some contexts, for example, the portable device 4540may comprise a syringe 3691 or other disposable item 3695. Alternativelyor additionally, the portable device 4540 may comprise a drug dispenser3270 configured (as a therapeutic module 4541, e.g.) to facilitate amedicinal component 4011 of regimen 2338. In some contexts, moreover,input module 3628 may transmit an affirmative decision 2508 (to network4090, e.g.) to associate the particular medical device with patient 4550after transmitting an automated prompt 2379 (like “Please press or say‘1’ to confirm that X should be used to perform Y upon patient Z”expressed via speaker 2057, e.g.) to caregiver 991 and as a direct andconditional response to receiving an affirmative reply (“1,” e.g.).

Intensive operation 92 describes obtaining an indication that themedical device is in a vicinity of the first patient (e.g. one or moresensors 3506, 4543 generating an indication 2488 that portable device4540 is within a vicinity 4585 of patient 4550). This can occur, forexample, in a context in which another portable device 4575 is carriedor worn by patient 4550; in which portable device 4540 approachespatient 4550 or in which patient 4550 approaches portable device 4540;in which such approach or proximity is detected by the one or moresensors 3506, 4543 (optically or by radio frequency or other short rangecommunication between devices, e.g.); and in which a de facto vicinity4585 (of patient 4550, e.g.) is established by an effective range of theone or more sensors 3506, 4543 of one portable device detecting theother portable device. Alternatively or additionally, the medical devicemay include an authorization module 3794 (including a speech recognitionmodule 3427 or otherwise capable of recognizing biometric data 2540 ofpatient 4550, e.g.) configured to generate the indication 2488 ofproximity between the medical device and patient 4550 conditionally (asa selective response to recognizing an utterance or other audiblepattern 2532 detected at portable device 4540, e.g.) in sensor datareceived (via camera 3707 or microphone 3708, e.g.) from a nearbypatient 4550.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for determining by wireless communication which devices are ina region as described herein without undue experimentation. See, e.g.,U.S. Pat. No. 8,064,884 (“System and method for provisioning a wirelessdevice to only be able to access network services within a specificlocation”); U.S. Pat. No. 8,010,126 (“Surveying wireless device users bylocation”); U.S. Pat. No. 7,983,677 (“Location-based wireless messagingfor wireless devices”); U.S. Pat. No. 7,979,086 (“Virtual visitorlocation register for a wireless local area network”); U.S. Pat. No.7,809,378 (“Location visit detail services for wireless devices”); U.S.Pat. No. 7,548,158 (“First responder wireless emergency alerting withautomatic callback and location triggering”); U.S. Pat. No. 7,539,500(“Using cell phones and wireless cellular systems with locationcapability for toll paying and collection”); U.S. Pat. No. 7,385,516(“Location visit confirmation services for wireless devices”); U.S. Pat.No. 7,068,992 (“System and method of polling wireless devices having asubstantially fixed and/or predesignated geographic location”); and U.S.Pat. No. 6,957,076 (“Location specific reminders for wireless mobiles”).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for computing a difference between locations as describedherein without undue experimentation. See, e.g., U.S. Pat. No. 8,044,798(“Passive microwave speed and intrusion detection system”); U.S. Pat.No. 8,026,850 (“Apparatus and method for computing location of a movingbeacon using time difference of arrival and multi-frequencies”); U.S.Pat. No. 7,962,283 (“Deviation-correction system for positioning ofmoving objects and motion tracking method thereof”); U.S. Pat. No.7,778,792 (“Systems and methods for location, motion, and contactdetection and tracking in a networked audiovisual device”); U.S. Pat.No. 7,775,329 (“Method and detection system for monitoring the speed ofan elevator car”); U.S. Pat. No. 7,671,795 (“Wireless communicationsdevice with global positioning based on received motion data and methodfor use therewith”); U.S. Pat. No. 7,647,049 (“Detection of highvelocity movement in a telecommunication system”); U.S. Pat. No.7,460,052 (“Multiple frequency through-the-wall motion detection andranging using a difference-based estimation technique”); U.S. Pat. No.7,242,462 (“Speed detection methods and devices”); U.S. Pat. No.6,985,206 (“Baseball pitch speed measurement and strike zone detectiondevices”); U.S. Pat. No. 6,400,304 (“Integrated GPS radar speeddetection system”).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for determining whether a device is in a location or region asdescribed herein without undue experimentation. See, e.g., U.S. Pat. No.8,019,168 (“Motion detecting device and search region variable-shapedmotion detector”); U.S. Pat. No. 8,000,723 (“System of utilizing cellinformation to locate a wireless device”); U.S. Pat. No. 7,986,237(“Location management method using RFID series”); U.S. Pat. No.7,932,830 (“Method of assigning and deducing the location of articlesdetected by multiple RFID antennae”); U.S. Pat. No. 7,605,688 (“Vehiclelocation determination system using an RFID system”); U.S. Pat. No.7,573,369 (“System and method for interrogating and locating atransponder relative to a zone-of-interest”); U.S. Pat. No. 7,525,425(“System and method for defining an event based on relationship betweenan object location and a user-defined zone”); U.S. Pat. No. 7,046,162(“Method and apparatus to locate a device in a dwelling or otherenclosed space”); and U.S. Pat. No. 6,205,326 (“Method for determiningwhen a communication unit is located within a preferred zone”).

Extensive operation 58 describes enabling the medical deviceconditionally, partly based on the indication that the order associatesthe first patient with the medical device and partly based on theindication that the medical device is in the vicinity of the firstpatient (e.g. configuration module 3704 transmitting a trigger 2302 tothe medical device in response to either a positive indication 2488 oran affirmative decision 2508, whichever is received later). This canoccur, for example, in a context in which the medical device is aportable device 4540 that include an electromechanical disablementfeature 3365 (a valve 3361 or latch 3362, e.g.) that prevents one ormore therapeutic modules 4541 (a syringe 3691 or inhaler 3692 or bag3693, e.g.) or data acquisition modules 4542 thereof from functioning(administering a drug 141 or diagnostic protocol, e.g.) until portabledevice 4540 receives trigger 2302 (a wireless device enablement signal2562, e.g.); and in which configuration module 3704 includes an “AND”gate configured to transmit the trigger 2302 and to receive theindication 2488 and decision 2508 upon which it is based. Some variantsof configuration module 3704 may respond to one or more other Booleanvalues also in some variants, such as in a configuration in which one ormore additional determinants 2394, 2395 as described above are alsoconfigured as “AND” gate inputs. Alternatively or additionally, in someimplementations, one or more inputs of configuration module 3704 may belatched independently (configured to remain “set” once activated, forexample, so that trigger 2302 might be transmitted even if indication2488 and decision 2508 are manifested as positive signals that do notoverlap in time, e.g.). In some contexts, moreover, invocation module2795 may be configured to coordinate flow 5500 automatically (withoutfurther input from any user local to the medical device, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for implementing an equipment failsafe as described hereinwithout undue experimentation. See, e.g., U.S. Pat. No. 8,083,406(“Diagnostic Delivery Service”); U.S. Pat. No. 8,070,739 (“Liquid drugtransfer devices for failsafe correct snap fitting onto medicinalvials”); U.S. Pat. No. 8,068,917 (“Fail-safe programming for implantablemedical device”); U.S. Pat. No. 7,752,058 (“Portable terminal and healthmanagement method and system using portable terminal”); U.S. Pat. No.7,696,751 (“Method and apparatus for ferrous object and/or magneticfield detection for MRI safety”); U.S. Pat. No. 7,438,072 (“Portablefield anesthesia machine and control therefore”); U.S. Pat. No.7,087,036 (“Fail safe system for operating medical fluid valves”); U.S.Pat. No. 7,034,934 (“Anti-carcinogenic lights and lighting”); U.S. Pat.No. 6,768,420 (“Vehicle compartment occupancy detection system”); andU.S. Pat. No. 6,366,809 (“Defibrillator battery with memory and statusindication gauge”).

With reference now to FIG. 46, shown is another example of a system 4600in which one or more technologies may be implemented. A wall-mountedintercom 3959 or other kiosk 4630 configured to facilitate patientintake (at a hospital 4602 or clinic, e.g.) may interact variouspatients 3950, 4250 or caregivers 4691. In some variants, kiosk 4630 mayinclude one or more dispensers 4633 configured to dispense a wearablearticle (a sticker 4634, wristband, facemask, or other such article2910, e.g.) customized with patient data (in a magnetic strip orink-printed surface 2427 thereof, e.g.) as described below. Kiosk 4630may likewise include one or more inputs (a camera 4631 or button 2079 ormicrophone 3508, e.g.) and one or more other outputs (a display 4626configured to provide video or other visual prompts recognizable by adeaf caregiver 4691, e.g.) to facilitate usage with a monolingual orother user who requires a particular protocol for effectiveintercommunication. A speaker 3509 may be provided, for example, tofacilitate auditory intercommunications (with a Spanish-speaking agent4691 or an English-speaking agent 4692 at a remote call center 4695,e.g.) via network 4690. Alternatively or additionally, kiosk 4360 may beadapted to display one or more countdown timers 2310 each relating to atask of apparent urgency (a remaining portion of a two-minute timeinterval associated with emergency personnel arriving at kiosk 4630 or alonger interval 2544 associated with maintenance personnel arriving atkiosk 4630, e.g.) made evident by kiosk input data. See FIGS. 56-57.

With reference now to FIG. 56, shown is a high-level logic flow 5600 ofan operational process. Intensive operation 83 describes causing a firstindividual to receive a playable prompt that was automatically selectedaccording to a first data component received from the first individual(e.g. response module 3664 causing one or more audio or video prompts2376, 2377 to be played to a patient or to his caregiver via a kiosk4630 in a hospital 4602). This can occur, for example, in a context inwhich medium 2305 and response unit 3605 implement a telephonic or othervoice menu system (resident in kiosk 4630 or in network 4690, e.g.); inwhich the “first” data component is a spoken term 2351 (“a dose,” e.g.)detected by microphone 3508; in which a speech recognition module 3427(along a signal path between microphone 3508 and selection module 3531and operably coupled thereto, e.g.) recognizes the spoken term (as beingon an English or Spanish word list associated with one or more callcenters 295, 4695 within network 4690, e.g.); in which network 290overlaps network 4690; and in which selection module 3531 indicates atleast one resource (call center 4695, e.g.) in response to speechrecognition module 3427 providing an indication 2489 that the spokenterm seems to be in English. In some contexts, for example, each suchresource selection may manifest a decision to present one or morecorresponding playable prompts 2376, 2377 (like “Press or say ‘two’ forEnglish,” e.g.) to the first individual (via a speaker 3509 of kiosk4630 or of a handheld 2841 or other user interface 2840, e.g.).Alternatively or additionally, speech recognition module 3427 may beconfigured to detect local physicians' names, symptom descriptors, orother probative terms 2352, 2353 (particular to a local medical practiceor other specific context, e.g.) based upon which selection module 3531can select a suitable prompt 2378. In some variants, moreover, selectionmodule 3531 may also select such prompts in response to one or moreother determinants 2391, 2392 (whether or not the first individual'svoice manifests distress or whether an English-speaking agent 4692 isapparently online, e.g.)

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for querying a user and recognizing a reply as describedherein without undue experimentation. See, e.g., U.S. Pat. No. 8,041,570(“Dialogue management using scripts”); U.S. Pat. No. 8,015,006 (“Systemsand methods for processing natural language speech utterances withcontext-specific domain agents”); U.S. Pat. No. 8,005,263 (“Hand signrecognition using label assignment”); U.S. Pat. No. 7,996,519(“Detecting content and user response to content”); U.S. Pat. No.7,983,611 (“Mobile device that presents interactive media and processesuser response”); U.S. Pat. No. 7,912,201 (“Directory assistance dialogwith configuration switches to switch from automated speech recognitionto operator-assisted dialog”); U.S. Pat. No. 7,778,816 (“Method andsystem for applying input mode bias”); U.S. Pat. No. 7,415,414 (“Systemsand methods for determining and using interaction models”); U.S. Pat.No. 7,346,555 (“Method and apparatus for client-in-charge businesstransaction processing”); U.S. Pat. No. 7,313,515 (“Systems and methodsfor detecting entailment and contradiction”).

In light of teachings herein, numerous existing techniques may also beapplied for configuring special-purpose circuitry or other structureseffective for recognizing voiced and other auditory signals as describedherein, or an absence thereof, without undue experimentation. See, e.g.,U.S. Pat. No. 8,036,735 (“System for evaluating performance of animplantable medical device”); U.S. Pat. No. 8,014,562 (“Signalprocessing of audio and video data, including deriving identifyinginformation”); U.S. Pat. No. 8,005,672 (“Circuit arrangement and methodfor detecting and improving a speech component in an audio signal”);U.S. Pat. No. 7,957,966 (“Apparatus, method, and program for soundquality correction based on identification of a speech signal and amusic signal from an input audio signal”); U.S. Pat. No. 7,899,677(“Adapting masking thresholds for encoding a low frequency transientsignal in audio data”); U.S. Pat. No. 7,856,289 (“Method and apparatusfor conserving power consumed by a vending machine utilizing audiosignal detection”); U.S. Pat. No. 7,809,559 (“Method and apparatus forremoving from an audio signal periodic noise pulses representable assignals combined by convolution”); U.S. Pat. No. 7,580,832 (“Apparatusand method for robust classification of audio signals, and method forestablishing and operating an audio-signal database, as well as computerprogram”); U.S. Pat. No. 7,557,728 (“Using audio to detect changes tothe performance of an application”).

Intensive operation 95 describes receiving a second data component fromthe first individual after the first individual received the playableprompt that was automatically selected according to the first datacomponent received from the first individual (e.g. detection module 3743receiving and recognizing an utterance of “two” from patient 4250 afterthe prompt 2377 of “Press or say ‘two’ for English”). This can occur,for example, in a context in which (an instance of) a computer 2670 orother data-handling device 3705 (implemented in network 4490, e.g.)includes interaction unit 3505 and in which detection module 3743 isconfigured to recognize a limited set of possible responses (keyed-in orspoken digits, e.g.). Alternatively or additionally, detection module3743 may be configured to recognize other medical intake data 3507 asthe “second” data component (vital signs, patient or caregiver responses2458 to diagnostic questions, audio or video clips of patient 4250,images 2577, or other diagnostic or authorization data from or about thefirst individual, e.g.) via other modes of input (a keyboard 846 orcamera 4631 or similar sensors of a data-handling device 3705, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for conducting a structured dialogue with a patient orcaregiver as described herein without undue experimentation. See, e.g.,U.S. Pat. No. 8,065,250 (“Methods and apparatus for predictiveanalysis”); U.S. Pat. No. 8,024,179 (“System and method for improvinginteraction with a user through a dynamically alterable spoken dialogsystem”); U.S. Pat. No. 7,610,556 (“Dialog manager for interactivedialog with computer user”); U.S. Pat. No. 7,539,656 (“System and methodfor providing an intelligent multi-step dialog with a user”); U.S. Pat.No. 7,461,000 (“System and methods for conducting an interactive dialogvia a speech-based user interface”); and U.S. Pat. No. 7,114,954(“Interaction education system for teaching patient care”).

Extensive operation 54 describes causing a wearable article at a firstcare facility to indicate the second data component received from thefirst individual after the first individual received the playable promptthat was automatically selected according to the first data componentreceived from the first individual (e.g. configuration module 3702causing a wearable sticker 4634 or wrist band 1223 at the “first” carefacility to include intake data 3507 from or about patient 4250). Thiscan occur, for example, in a context in which the first care facility isan ambulance 1295 or nursing home or hospital 4602; in which the firstindividual is a caregiver 4691 or patient 4250; in which theconfiguration module 3702 transmits a trigger 2301 that includes atleast the “second” data component; and in which such effective patientintake could not otherwise be automated. In some variants, for example,an on-site machine (dispenser 4633, e.g.) may encode such information inor on the wearable article (in a barcode or magnetic stripe, e.g.) inresponse to such a trigger. In some contexts, moreover, invocationmodule 2795 may be configured to coordinate flow 5600 automatically(without further input from any user local to hospital 4602, e.g.).

With reference now to FIG. 47, shown is another example of a system 4700in which one or more technologies may be implemented. A stationary orother countdown timer 4740 is mounted on a wall in a vicinity (hospitalroom 4704, e.g.) of one or more patients 4750. As shown, for example,countdown timer 4740 is configured so that a counterclockwise-movingelement (relative to an interior of room 4704, e.g.) has a position 4747that manifests a remaining time interval 2541 (about 22 minutes, e.g.).In various implementations, countdown timer 4740 is controlled by one ormore modules (of an interaction unit 3505 resident in network 4790,e.g.) having access to one or more protocol definitions 4771, 4772, 4773each comprising one or more records 4761, 4762, 4763 having one or moretask definition components 4781 (specifying what needs doing, e.g.)mapped to one or more corresponding timing components 4782 (specifyingwhen it is to be done, e.g.). In a context in which a task definitioncomponent 4781 comprises responding to an activation of a call control4730 in some device-detectable manner, for example, a timing component4782 may specify a standard time interval (thirty minutes, e.g.) withinwhich it is expected that at least one corresponding task (authorizedpersonnel resetting a call switch within room 4704 or activating anintercom in room 4704, e.g.) will be complete.

With reference now to FIG. 57, shown is a high-level logic flow 5700 ofan operational process. Intensive operation 91 describes identifying afirst health regimen associated with a first individual, the firsthealth regimen including one or more healthcare-related tasks associatedwith a time interval (e.g. interface module 3514 receiving an order 2516or other manifestation of a decision 2509 about a caregiver 991 havingprescribed one or more regimens 2338, 2339 including one or more timingcomponents 4782 for the treatment of patient 4750). This can occur, forexample, in a context in which caregiver 991 enters the order 2516directly via system 941; in which regimen 2338 is defined to include atleast one task 2443 (a medicinal component 4011 manifested in one ormore records 4761, 4762, e.g.) having a task definition component 4781and a timing component 4782; in which protocol definition 4771 calls foreither a caregiver 1391 to administer an injection of a first steroid ordose (as a task definition 4781 of record 4761, e.g.) or for patient4750 to ingest a second steroid or dose (as a task definition 4781 ofrecord 4762, e.g.); and in which the corresponding time interval ends at1 pm. This can occur, for example, either in a context in which thenominal time of administration is 1 pm (as a strict formal designation2501 of the time interval ending, e.g.) or in which records 4761-4763allow for a one hour margin (in which the nominal time of administrationis at noon as an informal designation 2502, e.g.). Alternatively oradditionally, some or all such records 4761-4763 may be derived from aninput module 3623 configured for optical character recognition upon ascan of a hard copy 877 (entered via scanner 878, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for determining and recording whether scheduled events arehappening within a given interval of time as described herein withoutundue experimentation. See, e.g., U.S. Pat. No. 7,369,476 (“Device forreading from or writing to optical recording media having a control unitfor a data slicer”); U.S. Pat. No. 7,335,106 (“Closed-loop system fordisplaying promotional events and granting awards for electronic videogames”); U.S. Pat. No. 7,330,101 (“Prescription compliance device andmethod of using device”); U.S. Pat. No. 7,293,645 (“Method formonitoring hand hygiene compliance”); U.S. Pat. No. 7,287,031 (“Computersystem and method for increasing patients compliance to medical careinstructions”); U.S. Pat. No. 7,271,728 (“Method for assessingimprovement in hand hygiene practices”); U.S. Pat. No. 7,170,823(“Medical dispenser, a blister card for use in the dispenser and amethod of dispensing medical doses”); U.S. Pat. No. 6,973,371 (“Unitdose compliance monitoring and reporting device and system”); U.S. Pat.No. 6,882,278 (“Apparatus and methods for monitoring compliance withrecommended hand-washing practices”); U.S. Pat. No. 6,655,583 (“Medicalbilling method and system”); U.S. Pat. No. 6,514,200 (“Patientcompliance monitor”); U.S. Pat. No. 6,375,038 (“Dispenser having timingmeans, multisensory output and means of tracking usage number”); U.S.Pat. No. 6,371,931 (“Reflex tester and method for measurement of rangeof motion and peripheral vision”); U.S. Pat. No. 6,198,695 (“Eventmonitoring device”); U.S. Pat. No. 6,198,383 (“Prescription compliancedevice and method of using device”).

Extensive operation 60 describes causing a countdown timer to indicate aremaining portion of the time interval associated with the one or morehealthcare-related tasks visibly in a vicinity of the first individual(e.g. interface module 3515 configuring a countdown timer 4740 to depictor support one or more physical or virtual elements at a position 4747that visibly manifests a remaining time interval 2541 in the vicinity ofpatient 4750). This can occur, for example, in a context in which “thevicinity” substantially comprises an interior of the patient's room 4704or vehicle 4243 (that includes an article held or worn by patient 4750,e.g.); in which the remaining time interval 2541 is manifested as ashrinking area or difference (a wedge or arc of a needle or dialrelative to an ending position, e.g.); in which the remaining timeinterval 2541 has a conspicuous visual expiration indicator (a verticalposition or digital zero or empty hourglass, e.g.); and in which patient4750 would otherwise manifest inappropriate indifference (by failing tonote past compliance lapses and future regimen requirements, e.g.) oranxiety (by repeatedly activating call control 4730 needlessly, e.g.)about the various tasks of his health regimens.

Extensive operation 50 describes signaling a Boolean indication ofwhether or not any of the one or more healthcare-related tasksassociated with the time interval were performed within the timeinterval after the countdown timer has indicated the remaining portionof the time interval associated with the one or more healthcare-relatedtasks visibly in the vicinity of the first individual (e.g.communication module 3682 recording a Boolean indication 2557 signifyingthat task 2443 was not completed on time). This can occur, for example,in a context in which “any” refers to at least one of the one or morehealthcare-related tasks associated with the time interval; in whichcountdown timer 4740 indicated the remaining time interval 2541 in room4704 throughout the interval; in which regimen 2338 called for thetimely completion of task 2443 (or lack thereof) to be recorded (inrecords archive 920, e.g.) as a performance metric 4082 (for patient4750 or caregiver 1391 or her employer, e.g.); and in which evaluationof regimens and service providers 2710 (insurers or caregivers 991 whoprescribe regimens, e.g.) over a period of months or years wouldotherwise lack objectivity. In some contexts, moreover, theinstitutional presence of flow 5700 and countdown timers (in a carefacility or home care network, e.g.) may provide such caregivers 991better latitude to establish (by a suitable invocation of operation 91for configuring protocol definition 4772, e.g.) which timing components4782 of each new regimen are to be observed strictly (those for whichinterface module 3515 and communication module 3682 are both invoked,e.g.) and which are to be observed more casually (without operation 50or without operation 60, e.g.) or not at all. In some contexts,moreover, invocation module 2795 may be configured to coordinate flow5700 automatically (without further input from any user local to patient4750, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for implementing an automatic timestamp and recordation asdescribed herein without undue experimentation. See, e.g., U.S. Pat. No.8,000,979 (“Automated patient management system”); U.S. Pat. No.7,844,837 (“Electronic device and timer therefor with tamper event timestamp features and related methods”); U.S. Pat. No. 7,643,465 (“Methodfor insertion of time stamp into real time data within a wirelesscommunications network”); U.S. Pat. No. 7,289,651 (“Image reportingmethod and system”); U.S. Pat. No. 7,283,566 (“Method and circuit forgenerating time stamp data from an embedded-clock audio data stream anda video clock”); U.S. Pat. No. 7,257,158 (“System for transmitting videoimages over a computer network to a remote receiver”); U.S. Pat. No.7,100,210 (“Hood intrusion and loss of AC power detection with automatictime stamp”); U.S. Pat. No. 6,893,396 (“Wireless internet bio-telemetrymonitoring system and interface”); and U.S. Pat. No. 6,656,122 (“Systemsand methods for screening for adverse effects of a treatment”).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for determining whether specific input has been received froma person within a particular time interval as described herein withoutundue experimentation. See, e.g., U.S. Pat. No. 8,055,240 (“Method ofnotifying a caller of message confirmation in a wireless communicationsystem”); U.S. Pat. No. 8,045,693 (“Message reception confirmationmethod, communications terminal and message reception confirmationsystem”); U.S. Pat. No. 7,707,624 (“System for, and method of, provingthe transmission, receipt and content of a reply to an electronicmessage”); U.S. Pat. No. 7,483,721 (“Communication device providingdiverse audio signals to indicate receipt of a call or message”); U.S.Pat. No. 7,283,807 (“Method and telecommunication system for indicatingthe receipt of a data message”); U.S. Pat. No. 7,031,734 (“System andmethod for confirming short message service (SMS) message reception inmobile communication terminal”); U.S. Pat. No. 7,020,458 (“Method andtelecommunication system for indicating the receipt of a data message”);U.S. Pat. No. 6,553,341 (“Method and apparatus for announcing receipt ofan electronic message”); and U.S. Pat. No. 6,122,485 (“Method and systemfor confirming receipt of a message by a message reception unit”).

With reference now to flow 5800 of FIG. 58 and to other flows describedabove, in some variants, one or more of operations 5822, 5825 may beperformed in conjunction with intensive operations described above or inpreparation for one or more extensive operations described above.Alternatively or additionally, one or more of operations 5874, 5878,5879 may likewise be performed in response to one or more intensiveoperations described above or in conjunction with extensive operationsdescribed above.

Operation 5822 describes receiving a communication delay as data enteredby a user (e.g. input module 312 receiving data 2258 that includes delay2237 from an end user device 2015 or system 841, 941). This can occur,for example, in a context in which input module 312 comprisestransistor-based circuitry having an event-sequencing structure; inwhich the user 3780 is a caregiver or patient 4250 who operates animplementation of device 305 (data-handling device 3705, e.g.); in whichinput module 312 can accept such data 2258 as a user preference 725(e.g. by asking “when should we contact you?”); in which delay 2237comprises an integer number of days; and in which means for performingone or more intensive operations 35-46, 81-97 as described above includean implementation of device 305. Alternatively or additionally, one ormore input modules 311-319 may be configured to obtain other such data2258 as described herein. In one such configuration, for example, inputmodule 317 may be configured to let the user enter an e-mail address721, telephone number 722, or other contact information 720 manifestingone or more of the user's preferences 725 (to be used in operation 5874described below, e.g.).

Operation 5825 describes looking up a communication delay as a functionof a therapeutic protocol (e.g. lookup module 2021 returning delay 2237selectively in response to an indication that protocol 130 is being usedfor treating someone). This can occur, for example, in a context inwhich lookup module 2021 comprises transistor-based circuitry having anevent-sequencing structure; in which means for performing one or moreintensive operations 35-46, 81-97 as described above include animplementation of device 2005; in which a data component 127 associatedwith a different therapeutic protocol 120 includes a communication delay2227 of 2.0 hours (as a digital expression, e.g.); in which one or moredata components 137, 138 specifically associated with therapeuticprotocol 130 each includes a communication delay 2237 that is more than2.0 hours; and in which an appropriate entity (a caregiver 1391 orexpert consultant, e.g.) has determined that such a communication delay2237 will be more effective (than a shorter delay 2227, e.g.) followinga triggering event (an order or administration, e.g.) for elicitingparticipation from a population of patients or caregivers who adopt atherapeutic protocol 130. In some contexts, for example, a table ofsuitable communication delays 2226, 2236, 2227, 2237 may be estimated(by a survey of experienced nurses or physician's assistants, e.g.) as amedian time within which each given condition 160, 170 typicallyproduces a detectable change in symptoms (relating to each respectiveprotocol, e.g.). In some contexts, moreover, a slightly longer period(by 1% to 50% or 1-3 standard deviations across a survey distribution,e.g.) may be preferable. Alternatively or additionally, the lookupresult (communication delay 2237, e.g.) may depend as a function of amedical condition (being shorter than a communication delay 2236associated with the same protocol 130 but a different condition 160,e.g.). Such a configuration of tabular data 3820 may be useful, forexample, in a context in which protocol 130 (taking anangiotensin-converting enzyme inhibitor, e.g.) typically provides afaster detectable response in treating condition 170 (shortness ofbreath, e.g.) than in treating condition 160 (leg swelling, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for implementing lookup functions as described herein withoutundue experimentation. See, e.g., U.S. Pat. No. 7,940,982 (“Method andapparatus for color space conversion using per-color selection oflook-up table density”); U.S. Pat. No. 7,921,088 (“Logical operationsencoded by a function table for compressing index bits in multi-levelcompressed look-up tables”); U.S. Pat. No. 7,916,137 (“Generation of 3Dlook-up tables for image processing devices”); U.S. Pat. No. 7,847,989(“Method for conversion of a colour space using separate chromatic andluminance look-up tables”); U.S. Pat. No. 7,706,034 (“Multi-Dimensionallook-up table generation via adaptive node selection based upon colorcharacteristics of an input image”); U.S. Pat. No. 7,558,961 (“Systemsand methods for embedding messages in look-up tables”); U.S. Pat. No.7,370,069 (“Numerical value conversion using a look-up table forcoefficient storage”); U.S. Pat. No. 7,346,642 (“Arithmetic processorutilizing multi-table look up to obtain reciprocal operands”); and U.S.Pat. No. 6,981,080 (“Look-up table based USB identification”).

Operation 5827 describes looking up a communication delay as a functionof a medical condition (e.g. lookup module 2022 selecting delay 2237 inresponse to an indication that a patient 4250 is being treated forcondition 170). This can occur, for example, in a context in whichlookup module 2022 comprises transistor-based circuitry having anevent-sequencing structure; in which a data component 136 associatedwith a different condition 160 (pathology, e.g.) includes acommunication delay 2236 of 2.0 calendar months (as a digitalexpression, e.g.); in which one or more data components 137, 147specifically associated with medical condition 170 each includes acommunication delay 2237 that is less than 2.0 calendar months; and inwhich an appropriate entity (a specialist or other physician, e.g.) hasdetermined that such a communication delay 2237 will be more effective(than a longer delay 2236, e.g.) following a triggering event (anestimated delivery time, e.g.) for eliciting participation from apopulation of caregivers 991, 4691 or patients 3950, 4250, 4450, 4550who treat or suffer from medical condition 170. Alternatively oradditionally, the lookup result (data component 137, e.g.) may depend asa function of a therapeutic protocol (having a communication delay 2237longer than that of a data component 127 associated with the samecondition 170 but a different protocol 120, e.g.). Such a configurationof tabular data may be useful, for example, in a context in whichtreating condition 170 (back pain, e.g.) with protocol 130 (a particularweightlifting exercise in a sauna, e.g.) will not generally permit anevaluation of treatment effectiveness as soon as that of protocol 120(medication, e.g.).

Operation 5874 describes transmitting a query as an automatic responseto an expiration of the communication delay (e.g. statement module 381transmitting one or more queries 571-574 relating to protocol 120 or tocondition 160 only after waiting for a time interval specified by delay2226). This can occur, for example, in a context in which one or more ofoperations 5822, 5825, 5827 have been performed; in which statementmodule 381 comprises transistor-based circuitry having anevent-sequencing structure; in which a prior communication (such as aninput 551-552 or query 571-574 or request 581, 582 or order 1018, 1118,2511-2516 or intercommunication 3441-3443) or other event describedherein tolled the beginning of the time interval and in which means forperforming one or more extensive operations 49-67 as described aboveinclude an implementation of device 305. Alternatively or additionally,in various embodiments, statement module 381 may be configured totrigger one or more other operations (extensive operations 49-67, e.g.)as described herein upon such expiration.

Operation 5878 describes causing an individual to be contacted by afallback mode of communication as a conditional response to receiving noreply from the individual by a prior mode of communication, the priormode of communication being telephonic (e.g. response module 354 takingno action if a reply 555 to a phone call 2291 is received before anexpiration of delay 541 but otherwise initiating another message 2290 tothe individual). This can occur, for example, in a context in whichresponse module 354 comprises transistor-based circuitry having anevent-sequencing structure; in which the delay 541 is on the order often seconds (within an order of magnitude, e.g.); in which the reply 555may take the form of a key press or utterance (as indicated in FIG. 10,e.g.) during the phone call 2291; and in which the fallback mode ofcommunication includes a delivery (by a fax or other machine 2030installed in the individual's home 289 or office or by an automaticallyplaced order to a third party with delivery instructions, e.g.) of aphysical article (in which message 2290 comprises one or more instanceof reminder letters or goods 691, e.g.) to the individual. Alternativelyor additionally, in a context in which a foreseeable reply 555 may takethe form of a return phone call 2291, e-mail message (containingspecific text 2292, or online session 3432 (via the Internet, e.g.), thedelay 541 may be on the order of one hour or one week (within 1 or 2orders of magnitude, e.g.).

Operation 5879 describes contacting an individual by a fallback mode ofcommunication as an automatic and conditional response to receiving noreply from the individual by a prior mode of communication, the fallbackmode of communication being telephonic (e.g. response module 355 takingno action if a reply 555 to a prior message 2290 is received within atime interval 538 but otherwise initiating a phone call 2291 to theindividual). This can occur, for example, in a context in which responsemodule 355 comprises transistor-based circuitry having anevent-sequencing structure; in which the prior message 2290 (comprisingtext 2292 or a phone query 571, e.g.) was sent by a request module 331,332 as described above; in which the prior message 2290 included ahyperlink 2296, menu option 2297, or other such control 2295 configuredto facilitate the individual providing input 552 to response module 355without the need to include any direct communication with otherindividuals; in which the time interval 538 began when the prior message2290 was sent; in which response module 355 infers the “receiving noreply from the individual” if the time interval 538 ends without suchinput 552; and in which means for performing one or more extensiveoperations 49-67 as described above include an implementation of device305. In some implementations, for example, the time interval 538 may beon the order of 3.0 days or of 3.0 months (within an order of magnitude,e.g.). Alternatively or additionally, response module 355 may beconfigured (as an auto-dialer, e.g.) to initiate a phone call 2291 orother intercommunication 3441-3443 between a call center 295 and theindividual (a caregiver or patient 4250, e.g.) as an automatic responsepartly based on the time interval 538 having expired and partly based onan immediate availability of a call center agent 294 (manifested as anindication 684 of the agent's current status, e.g.).

With reference now to flow 5900 of FIG. 59 and to other flows describedabove, in some variants, one or more of operations 5924, 5926 may beperformed in conjunction with intensive operations described above or inpreparation for one or more extensive operations described above.Alternatively or additionally, one or more of operations 5971, 5975 maylikewise be performed in response to one or more intensive operationsdescribed above or in conjunction with extensive operations describedabove.

Operation 5924 describes updating a locally-resident subscriber registryin response to an individual entering a service zone (e.g. update module2028 adding an identifier 733 of the individual to a registry 109 storedon a medium 105 in service zone 207 in response to an indication 683that the individual has entered service zone 207). This can occur, forexample, in a context in which update module 2028 comprisestransistor-based circuitry having an event-sequencing structure; inwhich the individual is a patient 1392, 4250 as described herein; inwhich service zone 207 is a defined region (a county or metropolitanarea, e.g.); in which device 2005 is on network 290; in which device2015 is held or worn by patient 4250; in which detection module 2042detects that patient 4250 has entered service zone 207 by comparing zonedescription data 2217 (defining service zone 207, e.g.) with GPS data752 indicating a current position of device 2015; in which detectionmodule 2042 responds by passing the indication 683 to update module2028; and in which means for performing one or more intensive operations35-46, 81-97 as described above include an implementation of device2005. Alternatively or additionally, one or more detection modules 2042,3741-3746 may be configured to determine whether the individual hasentered service zone 207 simply by detecting whether device 2015 iswithin a direct operating range of device 2005. See FIG. 45.

Operation 5926 describes obtaining an indication that a specificpathology in a particular individual has been treated at a firsthospital and an indication that the specific pathology in the particularindividual has been treated at a second hospital (e.g. retrieval module343 extracting a first record 671 indicating that patient 4450 was firsttreated at hospital 201 for pathology 181 and a second record 672indicating that the same patient 4250 was later treated at hospital 202for the same pathology 181). This can occur, for example, in a contextin which retrieval module 343 comprises transistor-based circuitryhaving an event-sequencing structure; in which retrieval module 343comprises one or more of the means for performing intensive operations35-46, 81-97 as described above; in which retrieval module 343 hasaccess to one or more records archives 820, 920 pertaining to treatmentsat both hospitals 201, 202; in which the institutional readmission(whichever was later, e.g.) and some suspect conditions (those that arenot objectively verifiable or even supported by evidence, e.g.) orprotocols (those that signal possible caprice or ulterior motivation onthe part of a patient or caregiver 4691, e.g.) together suggest apossibility of fraud or neglect that might warrant a clawback or paymentreduction for one or more hospitalizations or protocols; in which therecords 671, 672 identify one or more protocols 130, 140 performed inrelation to the specific pathology 181; and in which such records 671,672 pertaining to the particular individual (patient 4450, e.g.) bothidentify pathology 181 in an identical or sufficiently similar manner.Such a context can exist, for example, where retrieval module 343automatically recognizes identical or related pathology identifiers 511in use at both hospitals 201, 202. Alternatively or additionally, a user3780 who invokes retrieval module 343 (an auditor who has some cause tosuspect fraud or abuse, e.g.) may provide two or more instances ofpathology identifiers 511 (expressed as text strings 2281, 2282 of asearch term, e.g.) that are considered related, optionally with a nameor other identifiers of the particular individual (as another textstring 2283 of the search term, e.g.).

Operation 5971 describes retrieving a medical treatment record of oneindividual selectively in response to an explicit indication of apayment reduction that identifies the one individual (e.g. retrievalmodule 341 extracting whichever billing or other records 561-569,3191-3197 contain data components 127, 137, 147 pertaining to treatmentof a medical condition 170 of a specific patient 4250 at hospital 202 inresponse to an explicit indication 2113 of a potential or actual paymentreduction identifying the specific patient 4250). This can occur, forexample, in a context in which retrieval module 341 comprisestransistor-based circuitry having an event-sequencing structure; inwhich means for performing one or more extensive operations 49-67 asdescribed above include an implementation of device 305 (configured toinclude medical device configuration logic 3305, e.g.); in which thespecific patient 4250 has been identified by name 2111; in which thepayment reduction is indicated “explicitly” insofar that the indication2113 includes an audit identifier 2112 that CMS (Centers for Medicare &Medicaid Services, a federal agency within the United States Departmentof Health and Human Services) associates with payment reductions so thathospitals 201, 202 recognize the significance of the audit; in which oneor more such records 561-569, 3191-3197 reside in archive 820; and inwhich such retrieval is “selective” insofar that medical treatmentrecords of other individuals in the same archive 820 are not included inthe retrieval. This can occur, for example, in a context in which one ormore remote requestors 893, 993 (federal regulators, e.g.) have singledout an individual (patient 4250, e.g.) suspected of “excess”institutional readmissions. Under the healthcare system in the UnitedStates, for example, Section 3025 of Public Law 111-148 (the “PatientProtection and Affordable Care Act,” sometimes called “Obamacare”)states that, “ . . . beginning on or after Oct. 1, 2012, in order toaccount for excess readmissions in the hospital, the Secretary [ofHealth and Human Services] shall reduce the payments that wouldotherwise be made to such hospital . . . .”

Operation 5975 describes retrieving a medical treatment record relatingto a set of one or more pathologies selectively in response to anexplicit indication of a payment reduction that identifies the set (e.g.retrieval module 342 generating a report 2245 comprising numerous datacomponents 127, 128, 137, 138 relating particularly to a list or set 107of one or more medical conditions to be extracted from one or morerecords archives 820, 920 as an automatic response to a report request2246 that effectively identifies which medical conditions are beingaudited pursuant to a potential or actual payment reduction). This canoccur, for example, in a context in which retrieval module 342 comprisestransistor-based circuitry having an event-sequencing structure; inwhich at least one such condition 180 comprises a pathology 181associated with one or more specific text strings 2282, 2283 (e.g.“addict” or “stress disorder” listed in the subset of data components127, 128, 137, 138 comprising the report 2245) and in which thepotential or actual payment reduction is implicitly evident in a reporttype 521 (a readmission audit, e.g.), a request authorization 522(identifying a federal agency or other office responsible foridentifying or preventing payment reductions, e.g.), a user identifier523 (of a remote requestor 893, 993 who works for Medicare or Medicaid,e.g.), or other such indications 525; in which each data component inrecords archives 820, 920 includes one or more instances of records561-569, 3191-3197 described herein; and in which such retrieval is“selective” in that it excludes some records (in data component 126,e.g.) that reside in one or more records archives 820 based on theirrelation to a medical condition 160 that is not of interest.Alternatively or additionally, in some contexts, retrieval module 342may implement operation 5975 by executing a request (using search term2280, e.g.) that sets forth one or more pathological conditions 160(e.g. “injur” or “lacerat” expressed in an “ANDNOT” clause of a searchterm 2110, 2280) that are to be excluded from the report 2245.

With reference now to flow 6000 of FIG. 60 and to other flows 14-19,5800, 5900 described above, in some variants, one or more of operations6021, 6027 may be performed in conjunction with intensive operationsdescribed above or in preparation for one or more extensive operationsdescribed above. Alternatively or additionally, one or more ofoperations 6075, 6078 may likewise be performed in response to one ormore intensive operations described above or in conjunction withextensive operations described above.

Operation 6021 describes detecting a wireless device within an effectiverange of a stationary device (e.g. detection module 2046 determiningthat device 2015 is within an effective range of device 2005 byestablishing a wireless linkage 2011 with device 2015). This can occur,for example, in a context in which detection module 2046 comprisestransistor-based circuitry having an event-sequencing structure; inwhich means for performing one or more intensive operations 35-46, 81-97as described above include an implementation of device 2005 as astationary device that also implements device 242 (affixed to a buildingor other stationary structure, e.g.); in which device 2015 includes oneor more media as described above and an implementation of device 305that does not have a power supply (comprising a passive RFID transponder397, e.g.); and in which device 2015 is configured to respond to awireless signal from device 2005 by transmitting a unique wirelesssignal 2254 recognizable to detection module 2046 if device 2015 iswithin the effective range (linkage 2011, e.g.) of device 2005.Alternatively or additionally, in some contexts, device 2015 maycomprise a passive USID transponder 398 in a system configured asdescribed above, mutatis mutandis.

Operation 6027 describes obtaining an explicit indication whether arecord of treating a medical condition in a particular person with aparticular protocol contains any extrinsic evidence that treating themedical condition with the particular protocol has precedent (e.g.configuration module 325 receiving one or more yes/no values 2161, 2162from physicians or other caregivers 991, 1191 in response to one or morequeries 2171, 2172 directed to whether a patient's records 671-675included suitable annotations 2293 of extrinsic evidence in support ofany unconventional protocols 130, 140 prescribed or used by the patient4250). This can occur, for example, in a context in which configurationmodule 325 comprises transistor-based circuitry having anevent-sequencing structure; in which means for performing one or moreintensive operations 35-46, 81-97 as described above include animplementation of device 305; in which configuration module 325 directssuch a query to caregivers 991, 1191 who are editing one or more datacomponents 126, 136, 146 of the patient's medical record 674 (relatingto one or more protocols 120, 130, 140 being performed, e.g.); in whichconfiguration module 325 is configured to recognize one or moreprotocols 120 as conventional (standard or normal or common, e.g.); andin which configuration module 325 is configured to accept suchevidentiary content 432 (scans 811 or references or annotations 2293,e.g.) documenting any applicable precedent (research studies or reportsor prominence indications or anecdotal data, e.g.). In some contexts,configuration module 325 may require such content 432 or an affirmationof its existence (as value 2161, e.g.) before permitting such records674 to be saved, for example, or before permitting any order for otherprotocols 130, 140 (for non-emergency treatments, e.g.) to be placed.Alternatively or additionally, configuration module 325 may be operableto send a notification message 2290 to another entity 1091 (a hospitaladministrator, e.g.) as an automatic response to any unconventionalprotocol 140 being ordered by any caregiver at a particular hospital 202unless one or more such values 2161, 2162 are received (concerningextrinsic evidence and precedent, e.g.). In some contexts, moreover,configuration module 325 is itself configurable by such entities 1091such that each can control what kinds of notice they receive (byselectively subscribing to receive notices of unprecedented protocols140 being used with or without subscribing to receive notices ofunconventional-but-precedented protocols 130 being used, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for searching a collection of health-related treatments asdescribed herein without undue experimentation. See, e.g., U.S. Pat. No.8,010,664 (“Hypothesis development based on selective reported events”);U.S. Pat. No. 7,991,485 (“System and method for obtaining, processingand evaluating patient information for diagnosing disease and selectingtreatment”); U.S. Pat. No. 7,970,552 (“Diagnostic system for selectingnutrition and pharmacological products for animals”); U.S. Pat. No.7,959,568 (“Advanced patient management for identifying, displaying andassisting with correlating health-related data”); U.S. Pat. No.7,853,626 (“Computational systems for biomedical data”); U.S. Pat. No.7,630,762 (“Medical device with resuscitation prompts depending onelapsed time”); U.S. Pat. No. 7,485,095 (“Measurement and analysis oftrends in physiological and/or health data”); U.S. Pat. No. 7,181,375(“Patient data mining for diagnosis and projections of patient states”);and U.S. Pat. No. 6,665,558 (“System and method for correlation ofpatient health information and implant device data”).

Operation 6075 describes initiating a telephone call between a firstindividual and a second individual as an automatic response to the firstindividual not being compliant with a health regimen and to anindication that the second individual is available (e.g. response module358 creating a teleconference session or other phone call 2291 thatincludes patient 250 and agent 294 in response to an indication 686 thatpatient 250 is currently not compliant with one or more components 651,652, 4011-4016 of one or more health regimens 650, 2331-2339contemporaneously with an indication 687 of agent 294 being available toparticipate in the phone call 2291). This can occur, for example, in acontext in which response module 358 comprises transistor-basedcircuitry having an event-sequencing structure; in which means forperforming one or more extensive operations 49-67 as described aboveinclude an implementation of device 305; in which agent 294 providesindication 687 explicitly and directly to response module 358 (byclicking an “available” button on a desktop system 841, 941 thatimplements an auto-dialer, e.g.); in which such components 651, 652include at least one of a requirement (to use an exercise machine ortake particular drugs 141 or nutraceuticals, e.g.) or a restriction (torefrain from smoking, e.g.); and in which one or more devices 2005, 2015(comprising one or more sensors 2054, e.g.) signal compliance ornoncompliance with the regimen(s). A sensor activation can signalnoncompliance with a regimen component 651 that forbids snacking duringcertain hours, for example, by detecting a kitchen cupboard 2071opening. Alternatively or additionally, an implementation of sensor 2054can detect compliance with a regimen component 652 that requires a task(medication or exercise, e.g.) to be performed during a particular timeinterval 538 by detecting a movement in something associated with thetask (an exercise machine 2073 or drug dispenser actuator 2072 or “taskdone” button 2079 on a handheld 2074, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for detecting a movement of some or all of a device asdescribed herein without undue experimentation. See, e.g., U.S. Pat. No.8,082,122 (“Mobile device having a motion detector”); U.S. Pat. No.7,973,820 (“Motion detector and image capture device, interchangeablelens and camera system including the motion detector”); U.S. Pat. No.7,967,141 (“Device for the automatic detection of the movement ofobjects”); U.S. Pat. No. 7,887,493 (“Implantable device employingmovement sensing for detecting sleep-related disorders”); U.S. Pat. No.7,826,310 (“Acoustic navigation device and method of detecting movementof a navigation device”); U.S. Pat. No. 7,635,846 (“Motion detectordevice with rotatable focusing views and a method of selecting aspecific focusing view”); U.S. Pat. No. 7,511,260 (“Encoder device fordetecting movement”); U.S. Pat. No. 7,454,299 (“Device and method fordetecting an end of a movement of a valve piston in a valve”); and U.S.Pat. No. 6,920,699 (“Device for and method for detecting a relativemovement between two machine parts which are movable relative to oneanother”).

Operation 6078 describes signaling a decision whether to transfer aresource to a first individual partly based on an indication that thefirst individual is not compliant with a health regimen and partly basedon an indication that the first individual has accepted a telephone call(e.g. response module 357 transferring credits 693 into an account 616of patient 4250 in response to an indication 685 that patient 4250participated in a phone call 2291 with call center 295 about one or morehealth regimens 650, 2331-2339). This can occur, for example, in acontext in which response module 357 comprises transistor-basedcircuitry having an event-sequencing structure; in which an agent 294 ofcall center 295 participates in the phone call 2291; in which theresource (incentive 694, e.g.) is effective (large enough, e.g.) tomotivate a particular patient 4250 sometimes to take the call but notlarge enough to motivate the patient to violate the regimen; and inwhich a primary purpose of call center 295 is to initiate such telephonecalls in response to one or more signals 2253 (a device-generatednotification or webcam feed, e.g.) directly or indirectly indicatingthat a patient 4250 is apparently noncompliant with a time-criticalcomponent 651 (relating to dosages of an antibiotic, e.g.) of regimen.This can occur, for example, in a context in which patient 4250 complieswith the regimen component 651 in a portion of the patient's home 289that the call center agent 294 can monitor (via a camera 2053,microphone, or other sensor 2054, e.g.); in which patient 4250 has beeninformed of the incentives 694; in which an instance of device 305, 2005as described above resides in the patient's home 289 and on one or morenetworks described above; and in which response module 357 performsoperation 6078 by causing food or other goods 691 to be provided topatient 4250 (delivered to the patient's home 289 by a third-partysupplier who receives an order 618 from response module 357, e.g.) as anautomatic response to patient 4250 accepting the phone call from callcenter 295. Alternatively or additionally, an instance of device 305 maybe configured to deliver such goods 691 (in a dispensing machine 2030 atthe patient's home, e.g.).

With reference now to flow 6100 of FIG. 61 and to other flows 14-19,5800, 5900, 6000 described above, in some variants, one or more ofoperations 6121, 6123 may be performed in conjunction with intensiveoperations described above or in preparation for one or more extensiveoperations described above. Alternatively or additionally, one or moreof operations 6174, 6177 may likewise be performed in response to one ormore intensive operations described above or in conjunction withextensive operations described above.

Operation 6121 describes causing a locally-resident subscriber registryto be updated (e.g. invocation module 371 triggering update module 2028to remove an identifier 733 of the individual from a registry 109 storedon a medium 105 in service zone 207 in response to an indication 683that the individual is not in service zone 207). This can occur, forexample, in a context in which update module 2028 comprisestransistor-based circuitry having an event-sequencing structure; inwhich the individual is a patient 4250, 1292 as described herein; inwhich service zone 207 is a defined region (a county or metropolitanarea, e.g.); in which device 2005 is on network 290; in which device2015 is held or worn by patient 4250; in which invocation module 371detects that patient 4250 left service zone 207 by receiving anindication that patient 4250 is now in another service zone 208 (at home289, e.g.); and in which invocation module 371 responds by transmittinga request 772 for the removal of the individual from the registry 109.Alternatively or additionally, invocation module 371 and detectionmodule 2044 may be configured jointly to determine whether theindividual is still in service zone 207 simply by detecting whetherdevice 2015 (worn or carried by the individual, e.g.) is within a directoperating range of device 2005. Alternatively or additionally,invocation module 371 may be configured to invoke one or more otherfunctional modules as described with reference to flows herein.

Operation 6123 describes determining whether a portable device is in avicinity of another device (e.g. detection module 2041 detecting whethertwo devices 2005, 2015 are close enough that a sensor 2054 in one candirectly detect a transponder 1225 or other detectable structure 2075 ofthe other). This can occur, for example, in a context in which detectionmodule 2041 comprises transistor-based circuitry having anevent-sequencing structure; in which means for performing one or moreintensive operations 35-46, 81-97 as described above include animplementation of device 2005; in which one or both devices 2005, 2015implement an instance of device 305; in which detection module 2041 isconfigured to receive a signal 2252 from sensor 2054; in which suchdetection is “direct” insofar that a wireless linkage 2011 between thedevices 2005, 2015 consists of free space or other passive media (air,e.g.); and in which one or both devices 2005, 2015 are portable(configured to be worn or carried in one hand, e.g.). In some contexts,for example, a camera 2053 can transmit a signal 2252 (image, e.g.)indicating a detectable structure 2075 (a barcode or other visiblefeature that is unique to device 2015, e.g.) that detection module 2041is configured to recognize. Alternatively or additionally, one or moreother devices 241, 242 may be configured (e.g. as a tower or satelliteor wall-mounted device 1343, e.g.) to perform operation 6123 bydetecting both devices 2005, 2015 in a common location 204, 1304simultaneously and the two devices are “in a vicinity” of one anotherinsofar that both are within 50 meters of the same point (e.g. at a“third” device 241, 242).

Operation 6174 describes responding to an event with an audiblenotification (e.g. response module 353 causing speaker 2057 to signal acaregiver 1291, 1391 or other entity 1091 when one or more intensiveoperations 35-46, 81-97 are completed). This can occur, for example, ina context in which response module 353 comprises transistor-basedcircuitry having an event-sequencing structure; in which a device 305 orsystem 841, 941 described above includes an implementation of device2005. Alternatively or additionally, response module 353 may compriseone or more of the means for performing extensive operations 49-67 asdescribed above.

Operation 6177 describes responding to a payment-reduction eventrelating to a first medical treatment by causing a selective retrievalof one or more records that lack any prominence indication relating tothe first medical treatment from an archive that includes at least oneprominence indication relating to a second medical treatment (e.g.response module 352 responding to a request 582 for records 565, 566indicating that protocol 120 was administered but that lack anyprominence indications 1126, 1127 relating to protocol 120). This canoccur, for example, in a context in which response module 352 comprisestransistor-based circuitry having an event-sequencing structure; inwhich request 582 comprises a message from an entity that pays for atleast some of the first medical treatment (Medicare or Medicaid, e.g.)such as remote requestor 893 (an auditor or regulator, e.g.); in which areport type 521, request authorization 522, or other such indication 525signals a potential or actual payment-reduction event (manifesting areduction that has resulted or may result from a failure to justify theuse of protocol 120 in treating one or more specific medical conditions160, e.g.) and in which a single order 1018 for protocol 120 does notconstitute a “prominence indication” for purposes of determining whetherthe use of protocol 120 itself should be scrutinized (made subject to apayment reduction, e.g.). Alternatively or additionally, response module352 may invoke one or more retrieval modules 825, 925 configured toaccess at least one records archive 920 that contains a prominenceindication 1137 (average evaluation 1053 or use count 1054, e.g.) foranother protocol 130.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for identifying records relating to an unjustified action asdescribed herein without undue experimentation. See, e.g., U.S. Pat. No.7,793,835 (“System and method for identity-based fraud detection fortransactions using a plurality of historical identity records”); U.S.Pat. No. 7,668,843 (“Identification of anomalous data records”); U.S.Pat. No. 7,650,321 (“Two classifier based system for classifyinganomalous medical patient records”); U.S. Pat. No. 7,493,281 (“Automaticnotification of irregular activity”); U.S. Pat. No. 6,944,599(“Monitoring and automatic notification of irregular activity in anetwork-based transaction facility”); and U.S. Pat. No. 6,636,592(“Method and system for using bad billed number records to prevent fraudin a telecommunication system”).

With reference now to flow 6200 of FIG. 62 and to other flows 14-19,5800, 5900, 6000, 6100 described above, in some variants, one or more ofoperations 6224, 6229 may be performed in conjunction with intensiveoperations described above or in preparation for one or more extensiveoperations described above. Alternatively or additionally, one or moreof operations 6272, 6273, 6276 may likewise be performed in response toone or more intensive operations described above or in conjunction withextensive operations described above.

Operation 6224 describes detecting a passive wireless transponder withina vicinity of a vehicle (e.g. detection module 2043 receiving a returnsignal 2251 from a passive device implementing a radio frequencyidentification transponder 397 or an ultrasound identificationtransponder 398). This can occur, for example, in a context in whichdetection module 2043 comprises transistor-based circuitry having anevent-sequencing structure; in which medium 2205 comprises the passivedevice (a semiconductor chip or other device lacking a power supply2058, e.g.); in which one or more detection modules 2041-2046 resideaboard an ambulance 1295 (in device 1241, e.g.) or other vehicle (indevice 241, e.g.); and in which means for performing one or moreintensive operations 35-46, 81-97 as described above include animplementation of device 2005. Alternatively or additionally, detectionmodule 2043 (implemented in a stationary device 242, e.g.) may beconfigured to perform operation 6224 by detecting a passive wirelesstransponder that is aboard the vehicle (in device 1241, e.g.).

Operation 6229 describes obtaining an indication whether an individualis compliant with a health regimen (e.g. input module 318 receivingtiming data 453 relating to when a patient is taking medications athome). This can occur, for example, in a context in which input module318 comprises transistor-based circuitry having an event-sequencingstructure; in which one or more caregivers 991, 1191 prescribe a homecare regimen 650 and in which one or more particular components 652 ofthe regimen (antibiotics or other medications, e.g.) are crucial to afavorable outcome for a specific patient 4250. Alternatively oradditionally, input module 318 may be configured to provide additionaldata relevant to a determination of regimen compliance (raw data 712with one or more timestamps 711 from a sensor 2054 in the patient's home289, e.g.) into the patient's record 673. This can occur, for example,in a context in which there are one or more indications 685 (diagnosticdata 490 or protocol data 450, e.g.) that an institutional readmissionhas resulted from a behavior of a patient 4250 or at-home caregiver andnot from anything that occurred earlier (while in-patient at hospital201, e.g.).

Operation 6272 describes triggering a search of a particular recordsarchive by providing a selective search criterion, one that results inan exclusion of a first element in the particular records archive and aninclusion of a second element in the particular records archive (e.g.retrieval module 344 transmitting a search term 2110 to search engine2198 that searches records archive 820 and generates a search result2130 that excludes one or more data components 138 therein and includesone or more other data components 126 therein). This can occur, forexample, in a context in which retrieval module 344 comprisestransistor-based circuitry having an event-sequencing structure; inwhich search term 2110 identifies one or more selective inclusioncriteria 2101 (e.g. words or codes identifying condition 160) and one ormore selective exclusion criteria 2102 (e.g. words or codes identifyingprotocols 130, 140). Alternatively or additionally, retrieval module 344may be configured to trigger a search of other search records archive920 (by invoking retrieval module 925, e.g.) and to include the result2130 (in report 2244, e.g.).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for performing selective data retrieval as described hereinwithout undue experimentation. See, e.g., U.S. Pat. No. 8,068,603(“Focused retrieval of selected data in a call center environment”);U.S. Pat. No. 7,966,532 (“Method for selectively retrieving columnredundancy data in memory device”); U.S. Pat. No. 7,203,633 (“Method andsystem for selectively storing and retrieving simulation data utilizingkeywords”); U.S. Pat. No. 6,519,327 (“System and method for selectivelyretrieving messages stored on telephony and data networks”); U.S. Pat.No. 6,421,726 (“System and method for selection and retrieval of diversetypes of video data on a computer network”); U.S. Pat. No. 6,185,573(“Method and system for the integrated storage and dynamic selectiveretrieval of text, audio and video data”); U.S. Pat. No. 6,137,914(“Method and format for storing and selectively retrieving image data”);and U.S. Pat. No. 6,094,573 (“System and a method for selective dataretrieval from a remote database on basis of caller line identificationand user specific access codes”).

Operation 6273 describes transmitting a real-time notification to afirst person as an automatic response to an interface in a vicinity of asecond person detecting a particular event relating to the second person(e.g. update module 2029 transmitting one or more records 561-569,3191-3197, 671-675 or other data components 136-138 to the “first”person upon detecting an input 551, 552 or other action taken by the“second” person). This can occur, for example, in a context in whichupdate module 2029 comprises transistor-based circuitry having anevent-sequencing structure; in which the “first” person is a caregiver991, 1191, 1291 or patient 992, 4250 or administrator (a call centeragent 294 or other entity 1091, e.g.); in which the interface comprisesone or more of the above-described devices; in which such datacomponents 136-138 relate to the “second” person or to device 2005; inwhich the “particular event” comprises device 2015 entering a detectionrange of something carried or worn by the “second” person (manifestingthe vicinity of the 2nd person, e.g.); and in which means for performingone or more extensive operations 49-67 as described above include animplementation of device 2005. Alternatively or additionally, updatemodule 2029 may be configured to transmit such a notification (using ane-mail address 721 or telephone number 722, e.g.) in response to a“particular event” occurring within device 305 (comprising one or morecomputation or detection events described herein or a combinationthereof, e.g.). In some contexts, for example, update module 2029 may beconfigured to respond to one or more records 561-569, 3191-3197, 671-675as described herein being saved without a prominence indication orannotation 2293 (in a context in which the “second” person is acaregiver failing to document an unconventional treatment being ordered,e.g.).

Operation 6276 describes implementing a failsafe preventing medicalequipment from operating until an order associating the medicalequipment with a patient is received and until an indication is receivedthat the patient is in a vicinity of the medical equipment (e.g.detection module 2045 enabling medical equipment 2080 to function onlyafter receiving a report 2243 or other indication 688 that an authorizedcaregiver has generated such an order and only after detecting that thespecific patient 1392, 4250 is in a vicinity of the medical equipment2080). This can occur, for example, in a context in which detectionmodule 2045 comprises transistor-based circuitry having anevent-sequencing structure; in which one or more orders 1018, 618 asdescribed above call for particular diagnostic data 490 in relation topatient 4250; in which such orders explicitly or implicitly identify theequipment 2080 (corresponding to a particular biometric 481, test result482, computed tomography scan 483, or other image 484, e.g.) inassociation with the patient for whom they are to be obtained; in whichdetection module 2045 is configured to determine whether a location ordevice that includes a patient identifier 731, 1331 is in a vicinity ofthe equipment 2080; and in which detection module 2045 receivesindication 688 via input module 314. This can occur, for example, in acontext in which one or more detection modules 2041-2046 are mounted onthe equipment 2080 or in the same room (as a stationary instance ofequipment 2080, e.g.). In some contexts, moreover, a single device 305or room (office or server room, e.g.) or facility (hospital 201, e.g.)may be configured to contain an entire system described herein.Alternatively or additionally, an instance of detection module 2045configured to detect equipment 2080 may reside on the specific patient4250 or in a location associated with the patient 4250 (in the patient'sroom, e.g.). Alternatively or additionally, module 314 may be configuredto receive other data (one or more of indications 681-687, e.g.) ondata-handling media as described herein (at FIG. 4-7 or 21-26, e.g.).

Referring again to the flow variants of FIGS. 48 and 58-62 describedabove, intensive operation 93 may (optionally) be performed by a specialpurpose interface module 3513 implemented as circuitry 3044 having anevent-sequencing structure (an arrangement of transistors and voltagelevels in one or more semiconductor chips, e.g.) configured to generatea Boolean indication (implemented as a voltage level of a particularelectrical node 3484, e.g.) whether or not user 3780 is compliant withone or more regimens 2332-2336. This can occur, for example, in acontext in which such circuitry can determine apparent regimencompliance (positively or otherwise) based upon raw data (from a sampletester 3060 or camera 3707 or other sensors described herein, e.g.) orupon one or more test records 3196 (received from a technician 2761 whotests a fluid sample from user 3780, e.g.). In some variants, forexample, one or more such test records 3196 may be associated with arecord designation pattern 3841 (comprising a character or phonemesequence naming user 3780 or his caregiver and designating a specificrecord 3831 thereof, e.g.). Alternatively or additionally, tabular data3820 may include one or more recognizable human face patterns,fingerprint patterns 2531, retinal scan patterns, recognizable humanvoice or other audible patterns 2532, or other such biometric data 2540as a pattern 3841 that effectively designates another record 3832.Alternatively or additionally, tabular data 3820 may include one or moreserial numbers as a pattern 3841 (recited during a telephonic intakesession or other electronic intercommunication with caregiver 4691before his arrival at hospital 4602, e.g.) that effectively designatesanother record 3833.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for recognizing whether content matches a pattern as describedherein without undue experimentation. See, e.g., U.S. Pat. No. 8,005,875(“Automatic data transmission in response to content of electronic formssatisfying criteria”); U.S. Pat. No. 7,949,191 (“Method and system forsearching for information on a network in response to an image querysent by a user from a mobile communications device”); U.S. Pat. No.7,941,124 (“Methods of providing messages using location criteria andrelated systems and computer program products”); U.S. Pat. No. 7,689,705(“Interactive delivery of media using dynamic playlist generationsubject to restrictive criteria”); U.S. Pat. No. 7,668,647 (“Computermethod and apparatus for filling in an entry field using geographicalproximity and character criteria”); U.S. Pat. No. 7,580,952 (“Automaticdigital image grouping using criteria based on image metadata andspatial information”); U.S. Pat. No. 7,394,011 (“Machine and process forgenerating music from user-specified criteria”); U.S. Pat. No. 7,127,493(“Optimizing server delivery of content by selective inclusion ofoptional data based on optimization criteria”).

Also in such variants, extensive operation 55 may be performed by aspecial purpose configuration module 3702 implemented as or operablycoupled with circuitry 3317 having an event-sequencing structureconfigured to cause a wearable article to indicate a data component asan automatic and conditional response (operably coupled with asticker-printing dispenser 4633 or other machine at the “first” carefacility that can configure a wrist band 1223, badge 3851, item ofclothing, sticker 4634, or other such article to include the dataindicating the current health status, e.g.). This can occur, forexample, in a context in which the wearable article displays (via ascreen display 2426 or ink-printed surface 2427 thereof, e.g.) at leastsome of the designated record (indicating the current health status asone or more coded colors or barcodes 2918, e.g.) and in which (aninstance of) a computer 2670 or other data-handling device 3705 residesin one or more networks 3890 accessible to the first care facility.Moreover a wall-mounted kiosk 4630 or other stationary device 3760 (innursing home 3802, e.g.) configured to recognize the wearable articlemay, in some contexts, reside in network 3890.

Referring again to the flow variants of FIGS. 49 and 58-62 describedabove, intensive operation 81 may be performed by a special purposedetection module 3741 implemented as or operably coupled with circuitry3041 having an event-sequencing structure (an arrangement of transistorsand voltage levels in one or more semiconductor chips, e.g.) configuredto generate a Boolean indication (implemented as a voltage level of aparticular electrical node 3485 or a magnetic configuration of a storageelement on a disk drive, e.g.) whether or not an individual is compliantwith a regimen 2331-2339. This can occur, for example, in a context inwhich detection module 3741 is operably coupled with one or more of anadministration detection module 2848 (configured to detect compliancewith a medicinal component 4011, e.g.); a sample tester 3060 or othermeasurement equipment (configured to detect compliance with one or moremedicinal components 4011 or measurement components 4012 or omissioncomponents 4013, e.g.); specially-configured cupboards 2071 or smokedetectors 3958 or other environmental sensors 2054 (configured to detectcompliance with a dietary or other omission component 4013, e.g.);exercise machines 2073 (configured to detect compliance with an exercisecomponent 4014, e.g.); or other such special-purpose monitoringequipment 2080. In some contexts, for example, such a noncomplianceindication 2483 may comprise a percentage of events (of detection, e.g.)that were indicative of compliance being less than 100% or falling belowa threshold 2453 defined by a service provider 2710 (consultant orinsurance provider, e.g.).

Also in such variants, intensive operation 94 may (optionally) beperformed by a special purpose interface module 3511 implemented as oroperably coupled with circuitry 3273 having an event-sequencingstructure configured to provide a local Boolean indication (implementedas a voltage level of a particular electrical node 3486, e.g.) whetheror not an individual is available (at one or more remote call centers,e.g.). This can occur, for example, in a context in which a “high”voltage signifies that the “second” individual is available toparticipate in the electronic intercommunication 3442 and in which a“low” voltage signifies that the second individual may or may not beavailable to participate in the electronic intercommunication 3442.Alternatively or additionally, interface module 3511 may be configuredto generate a negative indication 2486 of availability as an automaticand conditional response to a signal 2565 (from a remote call center295, e.g.) indicating that an earpiece 3749 or other data-handlingdevice 3705 (configured to permit agent 3994 to speak to patient 3950 orhear her reply, e.g.) is offline or that a stationary zone (aworkstation or office in call center 3995, e.g.) is unoccupied.

Also in such variants, extensive operation 59 may be performed by aspecial purpose communication module 3681 implemented as or operablycoupled with circuitry 3314 having an event-sequencing structure(including an arrangement of transistors and voltage levels in one ormore semiconductor chips, e.g.) configured to initiate an electronicintercommunication 3441 (telephone call 3431, e.g.) between the firstand second individuals as an automatic and conditional response to aparticular combination of voltage levels of respective electrical nodes3485, 3486. This can occur, for example, in a context in whichcommunication module 3681 initiates such a telephone call 3431 byauto-dialing a handheld 2074 associated with the first individual or inwhich communication module 3681 automatically activates intercom 3959 sothat agent 3994 and patient 3950 can converse. Moreover in some variantsa particular agent 3994 may be able to maintain a ranked position sothat another available agent 294 will not be selected to participate inthe intercommunication 3441 with a particular first individual whileagent 3994 is available, perhaps fostering an effective rapport withparticular patients over time.

Referring again to the flow variants of FIGS. 50 and 58-62 describedabove, intensive operation 86 may be performed by a special purposeinterface module 3512 implemented as circuitry 3121 having anevent-sequencing structure (an arrangement of transistors and voltagelevels in one or more semiconductor chips, e.g.) configured to receive ascalar indication 2345 (a quantification from computation module 3772expressed via two or more electrical nodes 3472-3473, e.g.) of how wellpatient 992 has complied with a regimen 2334 that includes a medicinalcomponent 4011. This can occur, for example, in a context in which (aninstance of) a computer 2670 or other data-handling device 3705including a medium 2305 that resides in or on several networks 2790,3190 3590, 4090 and in which computation module 3772 generates thescalar indication 2345 as an inverse (reciprocal, e.g.) of another suchcompliance-indicative quantification described herein (e.g. indications2343, 2344) or as a sum or other aggregation of such values or as aninverse thereof.

Also in such variants, intensive operation 97 may be performed by aspecial purpose input module 3625 implemented as or operably coupledwith circuitry 3122 having an event-sequencing structure configured toreceive from care provider 2783 (a personal trainer, e.g.) a scalarindication 2346 (a ranking relative to other clients, e.g.) of how wella particular individual 2782 is currently complying with an exercisecomponent 4014 of a personalized regimen 2332. This can occur, forexample, in a context in which one or more available records 3191-3197provide contact information relating to providers who have recentlyserved the second individual (individual 2782, e.g.); in whichindividual 2782 has requested or otherwise authorized that suchproviders periodically provide regimen compliance information (bysubscribing or enrolling, e.g.) pursuant to program requirements (thatfacilitate flow 5000, e.g.) of a provider network; and in which the“second” device is a handheld device (owned by care provider 2783, e.g.)running a data-gathering app implementing such program requirements(automatically gathering scalar indications that may be missing orout-of-date, e.g.). In some contexts, for example, a program may providethat such evaluations become part of the particular individual's medicalrecord 3195 without a specific notification to the individual so thatthe individual will not have an occasion to exert pressure in regard tosuch ranking

Also in such variants, extensive operation 49 may be performed by aspecial purpose computation module 3771 implemented as circuitry 3322having an event-sequencing structure configured to compute a result 2312of arithmetically combining two or more scalar indications 2343-2349 (aweighted average having normalizing coefficients and offsets so thateach summand, for example, is effectively expressed as a percentage). Insome contexts, for example, a technician 2761 configures invocationmodule 2795 to identify which scalar indications to include in themathematical combination (by executing a search of all available records3191-3197, e.g.) to determine which patients (having various regimens2331-2339, e.g.) are currently being served by a particular entity(caregiver 991, e.g.) and thereby to obtain two or more scalarindications (by extracting or requesting such scalar values, e.g.)suitable for use by computation module 3771. Alternatively oradditionally, invocation module 2795 may be configured to transmit suchresults 2312 (as a conditional notification 4072 to service provider2710, e.g.) under one or more conditions 2302 (in response to result2312 exceeding a maximum threshold 2455 or falling below a minimumthreshold 2454, e.g.) defined by organizational management (relating toa class of caregivers, e.g.). Such embodiments may establish ameaningful advance over conventional monitoring, for example, incontexts in which diverse health regimens are in use and in whichdistinguishing between excellent and mediocre compliance facilitationstrategies by respective service providers 2710 would not otherwiseachieve much objectivity.

Referring again to the flow variants of FIGS. 51 and 58-62 describedabove, intensive operation 82 may be performed by a special purposedetection module 3744 implemented as circuitry 3052 having anevent-sequencing structure (an arrangement of transistors and voltagelevels in one or more semiconductor chips, e.g.) configured to recognizea person 4144 depicted in a portion 4172 of an image 4170. This canoccur, for example, in a context in which detection module 3744 isconfigured to execute facial recognition software (1) to define theportion 4172 that corresponds to a shape or color region generallyrecognizable as a person's face or (2) to determine a particular patientdesignation 2502 by matching the face visible within portion 4172 withfacial parameters of known patients (or both).

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for recognizing faces or other three-dimensional structures asdescribed herein without undue experimentation. See, e.g., U.S. Pat. No.7,925,058 (“Iris recognition system and method using multifocus imagesequence”); U.S. Pat. No. 7,873,189 (“Face recognition by dividing animage and evaluating a similarity vector with a support vectormachine”); U.S. Pat. No. 7,860,281 (“Method for the automaticrecognition of an object in an image”); U.S. Pat. No. 7,778,483(“Digital image processing method having an exposure correction based onrecognition of areas corresponding to the skin of the photographedsubject”); U.S. Pat. No. 7,706,068 (“Image three-dimensional recognitionapparatus”); U.S. Pat. No. 7,664,339 (“Image processing method forobject recognition and dynamic scene understanding”); U.S. Pat. No.7,345,574 (“Image recognition facilitated movable barrier operationsmethod and apparatus”); U.S. Pat. No. 7,239,275 (“Methods and systemsfor tracking signals with diverse polarization properties”); U.S. Pat.No. 7,092,566 (“Object recognition system and process for identifyingpeople and objects in an image of a scene”); U.S. Pat. No. 7,062,073(“Animated toy utilizing artificial intelligence and facial imagerecognition”); U.S. Pat. No. 6,831,993 (“Vehicle security systems andmethods employing facial recognition using a reflected image”).

Also in such variants, intensive operation 88 may be performed by aspecial purpose interface module 3516 implemented as or operably coupledwith circuitry 3131 having an event-sequencing structure (including anarrangement of transistors and voltage levels in one or moresemiconductor chips as described herein and operably coupled with a userinterface comprising a screen display 2426 and a user input, e.g.)configured to permit an individual (user 3780, e.g.) to select among twoor more portions 2581, 2582 of an image 2580 (visible on screen display2426, e.g.) via auditory or touchscreen input 2472. This can occur, forexample, in a context in which the image portion 2582 selected by user3780 depicts the first patient (user 3880, e.g.) or in a context inwhich user 3780 validates or otherwise selects image portion 2582verbally (by speaking “yes” or “option three” into microphone 3708,e.g.).

Also in such variants, extensive operation 51 may be performed by aspecial purpose triggering module 3552 implemented as or operablycoupled with circuitry 3318 having an event-sequencing structure(including an arrangement of transistors and voltage levels in one ormore semiconductor chips as described herein and operably coupled with aremote server or other network resource containing patient records3191-3197, e.g.) configured to retrieve and present medical data aboutthe first patient (user 3880 or person 4144, e.g.) as an automatic andconditional response (to user input 2471, 2472 selectively indicatingthe first patient, e.g.). This can occur, for example, in a context inwhich such medical data includes tabular data 3820 or other indications2341-2349 pertaining to the indicated patient as described herein; inwhich (an instance of) a computer 2670 or other data-handling device3705 (implemented in network 3890, e.g.) includes several storage orother media described above (in FIGS. 21-26, e.g.); and in which such“signaling” of operation 51 includes presenting such medical datavisually (via screen display 2426 or ink-printed surface 2427, e.g.) oraudibly (via earpiece 3749 or speaker 2057, e.g.). In some contexts,moreover, such medical data may include health status indicators 3842derived from secondary sources (from Facebook or similar socialnetworking websites, e.g.) on network 3890. Alternatively oradditionally, such “signaling” may include transmitting the medical datato a handheld or wearable data-handling device used by the first patient(user 3880, e.g.) or by another entity (user 3780, e.g.).

In some implementations of flow 5100, a camera 2053 (comprising astationary device 3760 or portable data-handling device 3705, e.g.) anda person (user 3780, e.g.) may perform operation 82 concurrently (in ahallway 3709 in which the first patient is visible, e.g.). This canoccur, for example, in a context in which the first patient is in viewof both user 3780 and camera 2053; in which another camera 3707 obtainsan image 2579 of user 3780 (at about the same time, e.g.) as the userinput 2471; and in which interface module 3516 includes a computationmodule 3773 configured to process such user input (images 2579, 2580,e.g.) to determine who user 3780 was pointing or looking at (as aparticular portion 4152 of a direct field of view 4150, e.g.) as theselective indication. Alternatively or additionally, a detection module3742 operably coupled to triggering module 3552 may be configured toidentify some all persons 4141-4144 visible within an image 4170 orother field of view 4150 (one by one, e.g.) and to indicate continuouslywhich such visible persons are fully identified (with green blinkingbrackets on touchscreen 4115, e.g.) or are not fully identified (withred or yellow blinking brackets on touchscreen 4115, e.g.) even beforeuser input 2471, 2472 selectively indicating the “first patient” isobtained. In some variants, for example, triggering module 3552 maypre-fetch the “medical data about the first patient” to a localdata-handling device 3705 in anticipation of receiving such user input2471, 2472. In some variants, data-handling device 3705 may beconfigured to forego operation 88 (conditionally) in contexts in which aparticular field of view 4150 includes only one patient (fullyidentified by detection module 3742, e.g.). Alternatively oradditionally, in some embodiments, data-handling device 3705 may includea mode control switch (implemented as a voltage level of a particularelectrical node 3483 that selectively enables or disables triggeringmodule 3552 from performing operation 51, e.g.) accessible to user 3780(so that data-handling device 3705 may continue to perform telephonic orother communication functions whether or not flow 5100 is fullyimplemented, e.g.). Moreover a wall-mounted kiosk 4630 or otherstationary device 3760 configured to interact with device 4110 may, insome contexts, reside on network 2790.

Referring again to the flow variants of FIGS. 52 and 58-62 describedabove, intensive operation 89 may be performed by a special purposeinput module 3624 implemented as or operably coupled with circuitry 3044having an event-sequencing structure (an arrangement of transistors andconductors in one or more semiconductor chips, e.g.) configured togenerate a Boolean indication 2551 (implemented as a voltage level of aparticular electrical node 3476, e.g.) whether or not patient 992 andher caregiver 991 are compliant with regimen 2334. This can occur, forexample, in a context in which detection module 3745 is configured togenerate indication 2551 by comparing one or more scalar indications2343-2345 against a minimum threshold 2454 (0.9 or 90%, e.g.) positivelyindicative of compliance or against a maximum acceptablefailure/violation rate (threshold 2455, e.g.) permitted by regimen 2334.

Also in such variants, intensive operation 96 may be performed by aspecial purpose triggering module 3551 implemented as or operablycoupled with circuitry 3271 having an event-sequencing structure(including an arrangement of transistors and voltage levels in one ormore semiconductor chips, e.g.) configured to notify patient 992 or hercaregiver 991 of an artificial incentive 2640 in response to a negativeindication 2989 of compliance with regimen 2334. This can occur, forexample, in a context regimen 2334 includes a training component,measurement component 4012, record keeping component, or other componentin which caregiver 991 participates and in which triggering module 3551responds to one or more positive indications 2987 or negativeindications 2989 of compliance by causing a system 941 belonging tocaregiver 991 to receive an electronic message 2290 (email or SMS textor voice message, e.g.) that includes an indication 2552 of theartificial incentive 2640 (one or more points 2616 or credits 2617 orother resources 2619, e.g.) offered in exchange for participating in adialog 3433 (with an agent 3994 of call center 3995, e.g.).Alternatively or additionally, triggering module 3551 may be configuredto initiate a text chat session 3432 (with patient 992 or caregiver 991via a service like “Instant Messenger” or on a handheld device, e.g.)with a bot-generated remark like “Hey, great job on keeping up with[regimen X]. You are eligible for [prize Y] if you take a quick survey.Are you interested?” Or in response to a regimen noncompliancedetermination 2988 triggering module 3551 may (optionally) be configuredto initiate the dialog 3433 with a bot-generated remark like “Say, wehave concerns about [regimen X] and we really need to talk to you. Infact, we'll give you [prize Y] just for having a chat with us. Are youinterested?” In such contexts, for example, the dialog 3433 may beestablished when the remark recipient (patient 992 or her caregiver 991,e.g.) provides a device-detectable affirmative reply (to agent 3994,e.g.). In light of teachings herein, those skilled in the art willrecognize various determinants 2394 suitable for establishing whether orwhen such dialog 3433 is adequately completed (agent 3994 acceptinganother task without signaling that the dialog 3433 was inadequate, eachparticipant saying or texting at least twenty words, agent 3994 enteringfive or more responses to survey questions during the dialog, dialog3433 lasting at least a minute, or other such device-detectable eventsmanifested in user input 2471, e.g.).

Also in such variants, extensive operation 53 may be performed by aspecial purpose authorization module 3792 implemented as or operablycoupled with circuitry 3328 having an event-sequencing structure(including an arrangement of transistors and voltage levels in one ormore semiconductor chips, e.g.) configured to authorize a dispensationof one or more tangible benefits 2620 (to patient 992 or her caregiver991, e.g.) if two specific conditions 2323, 2324 are met and otherwisegenerally not to authorize the dispensation. This can occur, forexample, in a context in which condition 2323 (manifested as a voltagelevel of a particular electrical node 3481, e.g.) comprises a regimencompliance determination 2986 (signaling that patient 992 and hercaregiver 991 are currently compliant with regimen 2334, e.g.) or othercompliance-positive indication 2987; in which condition 2324 (manifestedas a voltage level of one or more other electrical nodes 3482, e.g.)comprises one or more determinants 2394 signaling that dialog 3433occurred; in which authorization module 3792 is configured to authorizea physical dispensation (of a drug via dispenser 3270 or of currency viaATM 4410 or of other items via a machine 2030 mounted on a wall in anursing home 3802, e.g.) responsive to such conditions 2323, 2324; andin which timely communication about regimen compliance withintermittently available patients or caregivers would not otherwiseoccur. In some contexts, for example, authorization module 3792 mayimplement a partial withholding or other conditional access to arecreational drug (scotch, e.g.) or other treat (imported chocolates,e.g.) as an effective artificial incentive as described herein.Alternatively or additionally, in some embodiments, one or more otherconditions 2325 as described herein (the first individual being presentfor the dispensation, e.g.) may enable such dispensations. Alternativelyor additionally, in some embodiments, one or more other conditions 2328as described herein (the first individual refusing to receive thedispensation, e.g.) may disable such dispensations.

Referring again to the flow variants of FIGS. 53 and 58-62 describedabove, intensive operation 85 may be performed by a special purposeinput module 3626 implemented as circuitry 3042 having anevent-sequencing structure (an arrangement of transistors and voltagelevels in one or more semiconductor chips, e.g.) configured to generatea Boolean indication (implemented as a voltage level of a particularelectrical node 3474, e.g.) whether or not patient 4250 is compliantwith a minor requirement of regimen 2337 (violations of which areunlikely to have any precipitous consequences, e.g.) as described above.Also in such variants, intensive operation 90 may be performed by aspecial purpose input module 3627 implemented as or operably coupledwith circuitry 3043 having an event-sequencing structure configured togenerate a Boolean indication (implemented as a voltage level of aparticular electrical node 3475, e.g.) whether or not patient 4250 iscompliant with a major requirement of regimen 2337 (violations of whichare deemed by service provider 2710 to be likely to result in a majormedical consequence or in a loss of coverage, e.g.) as described above.

Also in such variants, extensive operation 52 may be performed by aspecial purpose triggering module 3553 implemented as or operablycoupled with circuitry 3313 having an event-sequencing structureconfigured to initiate one or more electronic intercommunications3441-3443 (involving one or more caregivers 1291, 1391 or their employeras described above, e.g.) automatically or otherwise as described above(as a real-time response to at least two “less significant” conditions2324-2326 being present but irrespective of at least one “moresignificant” condition 2327 being present or not, e.g.).

Also in such variants, extensive operation 56 may be performed by aspecial purpose authorization module 3791 implemented as or operablycoupled with circuitry 3311 having an event-sequencing structureconfigured to route one or more caregivers 1291, 1391 or their employerto a device associated with patient 4250 (a vehicle 4243 or wearablearticle 4245 or handheld 2074, e.g.) as an automatic and conditionalresponse to a “more significant” condition 2327 being present asdescribed above. In some variants, moreover, such routing (dispatchingan ambulance 1295, e.g.) may be conditional upon one or more additionaldeterminants 2395 (patient 4250 failing to respond to severalconsecutive attempts to initiate electronic intercommunications3441-3443 or other conditions 2329 as described above, e.g.).

Referring again to the flow variants of FIGS. 54 and 58-62 describedabove, intensive operation 84 may be performed by a special purposeresponse module 3663 (a logic gate, e.g.) operably coupled (throughrespective input signal paths, e.g.) to receive input from two otherresponse modules 3661, 3662. This can occur, for example, in a contextin which hospital 202 was a “qualifying” institution into which patient4250 was previously admitted (because he needed angioplasty forcongestive heart failure, e.g.); in which response module 3662 isimplemented as circuitry 2962 having an event-sequencing structureconfigured to provide a Boolean indication 2342 (implemented as avoltage level of a particular electrical node 3477, e.g.) whether or notpatient 4250 has yet experienced an institutional readmission (inrelation to the congestive heart failure or to an infection from theangioplasty procedure or to some other hospital-error-inducedcomplication, e.g.); and in which response module 3661 is implemented ascircuitry 2961 having an event-sequencing structure configured toprovide a Boolean indication 2341 whether or not patient 4250 has everbeen admitted to a qualifying institution (implemented as a voltagelevel representative of a “true” value to indicate that such admissionhad occurred, e.g.) operatively coupled with circuitry 3132 having anevent-sequencing structure configured to record an assignment of aresource 2619 as an automatic and conditional response (as described inoperation 84, e.g.). This can occur, for example, in a context in whichsuch indication 2342 is inverted (implemented as a voltage levelrepresentative of a “false” value to indicate that such readmission hadoccurred, e.g.); in which response module 3663 comprises an AND gate; inwhich a smaller (zero-value or negative, e.g.) artificial incentive willbe selected if the AND gate output is “false”; and in which a largerartificial incentive will be selected if the AND gate output is “true.”

Also in such variants, extensive operation 57 may be performed by aspecial purpose authorization module 3793 implemented as or operablycoupled with circuitry 3329 having an event-sequencing structure (anarrangement of transistors and voltage levels in one or moresemiconductor chips, e.g.) configured to authorize a dispensation if oneor more specific conditions are met and otherwise generally not toauthorize the dispensation. This can occur, for example, in a context inwhich such structure further comprises a vending machine 2030, ATM 4410,slot machine, or other electromechanical interaction unit 2775 capableof dispensing food, currency, or other resources 2619 directly topatient 4250 and in which such incentives 2640 would not otherwise beappropriately tailored (cost-effective, e.g.) for motivating patient4250 and others similarly situated to be proactive and diligent inavoiding such readmission. Alternatively or additionally, one or moreother flows described herein (for responding to noncompliance events orinteracting with patients, e.g.) may be used concurrently to notifypatient 4250 of applicable circumstances (reasons to follow a healthregimen, e.g.) or to adjust the incentive regimen so that the particularpatient 4250 will be more inclined to comply. In some instances, forexample, such patients 4250 may respond best to a negative incentivesuch as one in which a result 2313 of assigning “the component of theartificial incentive” may comprise a trigger 2306 that temporarilylimits the capabilities of one or more devices 2005, 2015 (establishinga maximum number of hours per day that a TV or phone will operate or amaximum speed at which a vehicle 4243 or data download will operate,e.g.) as a conditional response to an institutional readmission(resulting from health regimen noncompliance, e.g.). Even in contexts inwhich authorization module 3793 cannot feasibly control such devices2005, 2015 in real time, for example, such negative-incentive results2313 may be implemented by a suitable implementation of operation 57 inwhich an order is transmitted to a specialty service provider (mechanic,e.g.) to modify the device (by installing a speed governor, e.g.). SeeFIG. 53.

Referring again to the flow variants of FIGS. 55 and 58-62 describedabove, intensive operation 87 may be performed by a special purposeinput module 3628 implemented as circuitry 3261 having anevent-sequencing structure (an arrangement of transistors and voltagelevels in one or more semiconductor chips, e.g.) configured to provide aBoolean indication 2559 (implemented as a voltage level of a particularelectrical node 3478, e.g.) whether or not an order 4538 associates thefirst patient with the medical device. This can occur, for example, in acontext in which the “first” patient is a patient 4550 who might sufferharm if the regimen 2338 prescribed to her is not followed correctly; inwhich the medical device would otherwise present a significant hazard toanother particular patient 1292 (who has a heart condition or allergy orsimilar vulnerability, e.g.); or in which the medical device isexpensive and subject to degradation (disposable, e.g.). Someimplementations of operation 87 may cause one such medical device to beassociated with a particular list of two or more patients 4550, 4750.Other implementations of operation 87 may cause the first patient 4550to be associated with two or more such medical devices 2005, 2015(operably coupled via a network 4590 or via a direct linkage 2011,e.g.). In some variants, configuration module 3704 may be authorized tocause one or more such assignments to be undone selectively (when thetherapy or measurement is complete or the medical device is used or whenthe order is cancelled, e.g.).

Also in such variants, intensive operation 92 may be performed byspecial purpose circuitry 3051 having an event-sequencing structure(including an arrangement of transistors and voltage levels in one ormore semiconductor chips, e.g.) configured to generate a Booleanindication (implemented as a voltage level of a particular electricalnode 3479, e.g.) whether or not the first patient and the medical deviceare in proximity. This can occur, for example, in a context in which theevent-sequencing structure is configured to detect a location of themedical device or the first patient (or both) by virtue of beingoperably coupled with one or more sensors 3506, 4543 (via respectivesignal paths along which one or more digital signals 2564 may travel,e.g.) as described above. In a context in which the medical device is astationary device 2015 (an exercise machine 2073 in a particular room ofa nursing home 3802, e.g.), for example, the event-sequencing structuremay be implemented as a global positioning system (in GPS module 3420,e.g.) adapted to generate the Boolean indication (at electrical node3479, e.g.) whenever the special-purpose circuitry (of a portableprimary unit 3405 carried or worn by patient 4550 that implements localevent-sequencing logic 3005, e.g.) is in that particular room.

Also in such variants, extensive operation 58 may be performed by aspecial purpose configuration module 3704 implemented as or operablycoupled with circuitry 3327 having an event-sequencing structureconfigured to enable the medical device selectively in response to acombination of two or more indications (electrical nodes 3478-3480 allhaving a voltage level representative of a “set” or “true” Booleanvalue, e.g.) as described above (and otherwise doing nothing, e.g.).This can occur, for example, in a context in which the medical device isinitially disabled (so that it cannot function until operation 58,e.g.). Alternatively or additionally, configuration module 3704 may beconfigured to activate one or more disablement features 3365 of themedical device conditionally (responsive to one or more electrical nodes3480 having a voltage level representative of a “reset” or “false”Boolean value, e.g.). Moreover a wall-mounted kiosk 4630 or otherstationary device 3760 (in a room 4704 or hallway 3909 or other vicinity4585 of the first patient, e.g.) implementing the medical device may, insome contexts, reside in network 4590.

Referring again to the flow variants of FIGS. 56 and 58-62 describedabove, intensive operation 83 may be performed by a special purposeresponse module 3664 comprising a selection module 3532 implemented asor operably coupled with circuitry 2971 having an event-sequencingstructure (an arrangement of transistors and voltage levels in one ormore semiconductor chips, e.g.) configured to select a playable promptin response to input from or about a patient. This can occur, forexample, in a context in which selection module 3532 associates each ofmany diagnostic prompts 2371-2375 with a corresponding trigger pattern2361-2365; in which response module 3664 is configured so that each suchtrigger pattern spoken or entered by the first individual is recognized(via a touchscreen 4515 or speech recognition module 3427, e.g.) andtriggers a corresponding playable prompt 2371-2375 to be transmitted tothe first individual (via text-to-speech translation module 3428 andspeaker 3509, e.g.).

In some variants, for example, a spoken or otherwise recognized pattern2361 of “patient” (in a context in which no patient is currentlyselected, e.g.) may correspond to a playable prompt 2371 like “Pleasestate the name of the patient.” (A “patient” may generally be a mammalor other animal in scenarios described herein, unless the context of aparticular scenario strongly suggests that the patient must be human.)Likewise a spoken or otherwise recognized pattern 2362 of “Richard Hyde”(in a context in which the first individual has just heard prompt 2371,e.g.) may correspond to a playable prompt 2372 like “What is thepatient's date of birth?” Likewise a spoken or otherwise recognizedpattern 2363 of a calendar date (in a context in which the firstindividual has just heard prompt 2372 and in which a local medicalrecord 3194 is found for a Richard Hyde having that date of birth, e.g.)may correspond to a playable prompt 2373 like “Has Richard Hyde hadmedical care here before?” Likewise a spoken or otherwise recognizedpattern 2364 of “yes” (in a context in which the first individual hasjust heard prompt 2373, e.g.) may correspond to a playable prompt 2374like “Does Richard Hyde have any new symptoms today?” Likewise a spokenor otherwise recognized pattern 2365 of “yes” (in a context in which thefirst individual has just heard prompt 2374, e.g.) may correspond to aplayable prompt 2375 like “Please describe the primary health issue forwhich Richard Hyde needs care today.” Alternatively or additionally, oneor more such prompts 2371-2379 may be displayed (via a touchscreen 4515or display 4626 in a vicinity of the first individual, e.g.) and played(via speaker 3509, e.g.) simultaneously.

Also in such variants, intensive operation 95 may be performed by aspecial purpose detection module 3743 implemented as or operably coupledwith circuitry 3115 having an event-sequencing structure (including anarrangement of transistors and voltage levels in one or moresemiconductor chips comprising a video- or sound-clip capture module3426 operably coupled to a special-purpose speech recognition module3427, e.g.) configured to recognize a response after a prompt is playedto an individual. This can occur, for example, in a context in whichdetection module 3743 recognizes one or more patterns 2362-2366 that maycomprise the “second” data component. Alternatively or additionally, thesecond data component may include intake data 3507 comprisingunrecognized content (a sound clip or other biometric data notrecognized by detection module 3743, e.g.).

Also in such variants, extensive operation 54 may be performed by aspecial purpose configuration module 3702 implemented as or operablycoupled with circuitry 3316 having an event-sequencing structureconfigured to cause a wearable article to indicate a data component asan automatic and conditional response (operably coupled with asticker-printing dispenser 4633 or other machine at the “first” carefacility that can configure a wrist band 1223, bandage 3852, sticker4634, or other wearable article to include the “second” data component,e.g.). This can occur, for example, in a context in which the wearablearticle contains the second data component (as a video or audio clip inthe form of an encrypted or other digital data file on a flash drive,e.g.) and in which data-handling device 3705 resides in one or morenetworks as described above.

Referring again to the flow variants of FIGS. 57 and 58-62 describedabove, intensive operation 91 may be performed jointly by two specialpurpose configuration modules 3701, 3703. This can occur, for example,in a context in which configuration module 3701 is implemented ascircuitry 2972 having an event-sequencing structure (an arrangement oftransistors and voltage levels in one or more semiconductor chips, e.g.)configured to associate patient 4250 or user 3780 with a regimen 2339and in which configuration module 3703 is implemented as circuitry 3035having an event-sequencing structure configured to associate one or moretasks 2444 of regimen 2339 with a particular time interval 2542 (“2hours” or “from now until 7:30 pm,” e.g.). In some contexts, forexample, task 2444 may include conducting a counseling session (inperson or via data-handling device 3705, e.g.) between patient 4250 anduser 3780 (a nutritionist or other caregiver, e.g.).

Also in such variants, extensive operation 60 may be performed by aspecial purpose interface module 3515 implemented as or operably coupledwith circuitry 3262 having an event-sequencing structure configured tocause a countdown timer 2310 to progress (until an associated task iscomplete or the deadline has passed, e.g.). This can occur, for example,in a context in which countdown timer 2310 is implemented in one or morewearable articles 4245 (in which the countdown timer 2310 is displayedin a portion 4231 of an image 4230, e.g.) or other data-handling devices3705 (as a browser page or other remote real-time notification, e.g.);in which user 3780 has another such data-handling device 3705 (with atouchscreen 4115 or other display configured to implement countdowntimer 2310, e.g.); and in which patient 4250 and user 3780 are requiredto begin their session (per a task definition component 4781 of record4763, e.g.) by 7:30 pm (per a timing component 4782 of record 4763,e.g.). Moreover a computer 2670 or kiosk 4630 (having a stationarydisplay 4626 or similar suitable medium 2305, e.g.) may, in somecontexts, be configured to implement countdown timer 2310. Alternativelyor additionally, in some variants, such devices can include an image2576 that displays two or more instances of countdown timers 2310 sothat two or more respective time intervals 2542-2543 (associated withrespective healthcare-related tasks for which patient 4250 or hiscaregiver are responsible, e.g.) are visible simultaneously in thevicinity of the first individual.

In light of teachings herein, numerous existing techniques may beapplied for configuring special-purpose circuitry or other structureseffective for implementing a notification as described herein withoutundue experimentation. See, e.g., U.S. Pat. No. 8,060,562 (“Real timeupdate notification”); U.S. Pat. No. 7,940,602 (“Real-time system andmethod of underwater depth discrepancy detection, recordation and alarmnotification”); U.S. Pat. No. 7,924,149 (“System and method forproviding alarming notification and real-time, critical emergencyinformation to occupants in a building or emergency designed area andevacuation guidance system to and in the emergency exit route”); U.S.Pat. No. 7,899,739 (“Construction payment management system and methodwith real-time draw notification features”); U.S. Pat. No. 7,898,423(“Real-time event notification”); U.S. Pat. No. 7,890,622 (“Real-timenotification of device events”); U.S. Pat. No. 7,865,566 (“Method andapparatus for providing real-time notification for avatars”); U.S. Pat.No. 7,835,506 (“Method and system for real-time notification anddisposition of voice services in a cable services network”); U.S. Pat.No. 7,813,481 (“Conversation recording with real-time notification forusers of communication terminals”); U.S. Pat. No. 7,617,162 (“Real timepush notification in an event driven network”); and U.S. Pat. No.7,319,378 (“Anti-theft system for a vehicle with real-time notificationfeature”).

Also in such variants, extensive operation 50 may be performed by aspecial purpose communication module 3682 implemented as or operablycoupled with circuitry 3325 having an event-sequencing structureconfigured to transmit a Boolean indication 2557 whether or not the 7:30pm deadline (specified by timing component 4782 of record 4763, e.g.)was met. This can occur, for example, in a context in whichcommunication module 3682 is configured to transmit such data to recordsarchive 820 or to some other recipient 2722 (a family member of patient4250 or other subscriber, e.g.); in which the timely completion of suchtasks would not otherwise get an appropriate degree of attention; and inwhich Boolean indication 2557 is implemented (as a voltage level, e.g.)on an electrical node 3489 (of a response unit 3605 operatively coupledwith data-handling device 3705, e.g.). In some variants, for example,even a single such Boolean indication 2557 may be encoded (by a suitablecode division multiple access protocol, e.g.) to be expressed acrossseveral nodes (signal transmission lines, e.g.).

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and/or examples. Insofar as such block diagrams, flowcharts, and/orexamples contain one or more functions and/or operations, it will beunderstood by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or virtually any combination thereof. In one embodiment,several portions of the subject matter described herein may beimplemented via Application Specific Integrated Circuits (ASICs), FieldProgrammable Gate Arrays (FPGAs), digital signal processors (DSPs), orother integrated formats. However, those skilled in the art willrecognize that some aspects of the embodiments disclosed herein, inwhole or in part, can be equivalently implemented in integratedcircuits, as one or more computer programs running on one or morecomputers (e.g., as one or more programs running on one or more computersystems), as one or more programs running on one or more processors(e.g., as one or more programs running on one or more microprocessors),as firmware, or as virtually any combination thereof, and that designingthe circuitry and/or writing the code for the software and or firmwarewould be well within the skill of one of skill in the art in light ofthis disclosure. In addition, those skilled in the art will appreciatethat the mechanisms of the subject matter described herein are capableof being distributed as a program product in a variety of forms, andthat an illustrative embodiment of the subject matter described hereinapplies regardless of the particular type of signal bearing medium usedto actually carry out the distribution. Examples of a signal bearingmedium include, but are not limited to, the following: a recordable typemedium such as a floppy disk, a hard disk drive, a Compact Disc (CD), aDigital Video Disk (DVD), a digital tape, a computer memory, etc.; and atransmission type medium such as a digital and/or an analogcommunication medium (e.g., a fiber optic cable, a waveguide, a wiredcommunications link, a wireless communication link (e.g., transmitter,receiver, transmission logic, reception logic, etc.), etc.).

While particular aspects of the present subject matter described hereinhave been shown and described, it will be apparent to those skilled inthe art that, based upon the teachings herein, changes and modificationsmay be made without departing from the subject matter described hereinand its broader aspects and, therefore, the appended claims are toencompass within their scope all such changes and modifications as arewithin the true spirit and scope of the subject matter described herein.It will be understood by those within the art that, in general, termsused herein, and especially in the appended claims (e.g., bodies of theappended claims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.).

It will be further understood by those within the art that if a specificnumber of an introduced claim recitation is intended, such an intentwill be explicitly recited in the claim, and in the absence of suchrecitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to claims containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations. In addition, evenif a specific number of an introduced claim recitation is explicitlyrecited, those skilled in the art will recognize that such recitationshould typically be interpreted to mean at least the recited number(e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations).

Furthermore, in those instances where a convention analogous to “atleast one of A, B, and C, etc.” is used, in general such a constructionis intended in the sense one having skill in the art would understandthe convention (e.g., “a system having at least one of A, B, and C”would include but not be limited to systems that have A alone, B alone,C alone, A and B together, A and C together, B and C together, and/or A,B, and C together, etc.). In those instances where a conventionanalogous to “at least one of A, B, or C, etc.” is used, in general sucha construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, or C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that typically a disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms unless context dictates otherwise. For example, the phrase “Aor B” will be typically understood to include the possibilities of “A”or “B” or “A and B.”

This application may make reference to one or more trademarks, e.g., aword, letter, symbol, or device adopted by one manufacturer or merchantand used to identify and/or distinguish his or her product from those ofothers. Trademark names used herein are set forth in such language thatmakes clear their identity, that distinguishes them from commondescriptive nouns, that have fixed and definite meanings, or, in many ifnot all cases, are accompanied by other specific identification usingterms not covered by trademark. In addition, trademark names used hereinhave meanings that are well-known and defined in the literature, or donot refer to products or compounds for which knowledge of one or moretrade secrets is required in order to divine their meaning. Alltrademarks referenced in this application are the property of theirrespective owners, and the appearance of one or more trademarks in thisapplication does not diminish or otherwise adversely affect the validityof the one or more trademarks. All trademarks, registered orunregistered, that appear in this application are assumed to include aproper trademark symbol, e.g., the circle R or bracketed capitalization(e.g., [trademark name]), even when such trademark symbol does notexplicitly appear next to the trademark. To the extent a trademark isused in a descriptive manner to refer to a product or process, thattrademark should be interpreted to represent the corresponding productor process as of the date of the filing of this patent application.

With respect to the numbered clauses and claims expressed below, thoseskilled in the art will appreciate that recited operations therein maygenerally be performed in any order. Also, although various operationalflows are presented in a sequence(s), it should be understood that thevarious operations may be performed in other orders than those which areillustrated, or may be performed concurrently. Examples of suchalternate orderings may include overlapping, interleaved, interrupted,reordered, incremental, preparatory, supplemental, simultaneous,reverse, or other variant orderings, unless context dictates otherwise.Furthermore, terms like “responsive to,” “related to,” or otherpast-tense adjectives are generally not intended to exclude suchvariants, unless context dictates otherwise. Also in the numberedclauses below, specific combinations of aspects and embodiments arearticulated in a shorthand form such that (1) according to respectiveembodiments, for each instance in which a “component” or other suchidentifiers appear to be introduced (with “a” or “an,” e.g.) more thanonce in a given chain of clauses, such designations may either identifythe same entity or distinct entities; and (2) what might be called“dependent” clauses below may or may not incorporate, in respectiveembodiments, the features of “independent” clauses to which they referor other features described above.

Those skilled in the art will appreciate that the foregoing specificexemplary processes and/or devices and/or technologies arerepresentative of more general processes and/or devices and/ortechnologies taught elsewhere herein, such as in the claims filedherewith and/or elsewhere in the present application.

CLAUSES

1. (Independent) A healthcare information management system comprising:

one or more articles of manufacture including

transistor-based circuitry having an event-sequencing structureconfigured for causing a first individual to receive a playable promptthat was automatically selected according to a first data componentreceived from the first individual;

transistor-based circuitry having an event-sequencing structureconfigured for receiving a second data component from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual; and

transistor-based circuitry having an event-sequencing structureconfigured for causing a wearable article at a first care facility toindicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual.

2. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

a portable device associated with the first individual and including thetransistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual.

3. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

a data-handling medium bearing the first data component received fromthe first individual including a name of the first individual.

4. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

a data-handling medium bearing the first data component received fromthe first individual including a name of a second individual.

5. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

a microphone configured to receive audio data from the first individual;and

a data processing module configured to extract the first data componentfrom the audio data from the first individual.

6. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

a camera configured to receive image data from the first individual; and

a data processing module configured to extract the first data componentfrom the video data from the first individual.

7. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

a user interface including the transistor-based circuitry having theevent-sequencing structure configured for causing the first individualto receive the playable prompt that was automatically selected accordingto the first data component received from the first individual, the userinterface including a keyboard configured to receive the first datacomponent from the first individual.

8. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

a storage medium containing the playable prompt, the playable promptcomprising a digital data sequence.

9. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

a selection module configured to select the playable prompt responsiveto the first data component.

10. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

an invocation module configured to cause a remote entity to select theplayable prompt at least partly based on the first data component; and

an output module configured to play the playable prompt in a vicinity ofthe first individual.

11. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

a user interface including the transistor-based circuitry having theevent-sequencing structure configured for causing the first individualto receive the playable prompt that was automatically selected accordingto the first data component received from the first individual, the userinterface including a speaker configured to play an audio component ofthe playable prompt.

12. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

a user interface including the transistor-based circuitry having theevent-sequencing structure configured for causing the first individualto receive the playable prompt that was automatically selected accordingto the first data component received from the first individual, the userinterface including a display configured to play a video component ofthe playable prompt.

13. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the wearable article, comprising a data-handling medium configured tobear a Boolean indication of whether or not a task associated with thefirst individual and with a time interval was performed within the timeinterval.

14. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the wearable article, comprising a wrist band configured to indicate thesecond data component received from the first individual after the firstindividual received the playable prompt that was automatically selectedaccording to the first data component received from the firstindividual.

15. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the wearable article, comprising a printed surface configured toindicate information about the first individual, the informationcomprising the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual.

16. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the wearable article, comprising a barcode configured to indicate thesecond data component received from the first individual after the firstindividual received the playable prompt that was automatically selectedaccording to the first data component received from the firstindividual.

17. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the wearable article, comprising a data-handling medium configured toindicate a current health status, the current health status comprisingthe second data component received from the first individual after thefirst individual received the playable prompt that was automaticallyselected according to the first data component received from the firstindividual.

18. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

an application-specific integrated circuit, including thetransistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual.

19. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for looking up a communication delay as a function of        a therapeutic protocol associated with a recipient of the        therapeutic protocol, the recipient being or not being the first        individual; and    -   transistor-based circuitry having an event-sequencing structure        configured for transmitting a query as an automatic response to        an expiration of the communication delay.

20. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for looking up a communication delay as a function of        a medical condition associated with a recipient of the wearable        article, the recipient being or not being the first individual;        and    -   transistor-based circuitry having an event-sequencing structure        configured for transmitting a query as an automatic response to        an expiration of the communication delay.

21. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for causing an individual to be contacted by a        fallback mode of communication as a conditional response to        receiving no reply from the individual by a prior mode of        communication, the prior mode of communication being telephonic,        the individual being the first individual or a patient of the        first individual.

22. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for contacting an individual by a fallback mode of        communication as an automatic and conditional response to        receiving no reply from the individual by a prior mode of        communication, the fallback mode of communication being        telephonic, the individual being the first individual or a        patient of the first individual.

23. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for updating a locally-resident subscriber registry        in response to the first individual entering a service zone.

24. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for obtaining an indication that a specific pathology        in the first individual has been treated at a first hospital and        an indication that the specific pathology in the first        individual has been treated at a second hospital, the first care        facility being the first hospital.

25. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for retrieving a medical treatment record of the        first individual selectively in response to an explicit        indication of a payment reduction that identifies the first        individual.

26. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for retrieving a medical treatment record relating to        a set of one or more pathologies selectively in response to an        explicit indication of a payment reduction that identifies the        set.

27. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for detecting a wireless device within an effective        range of a stationary device, the wearable article being the        wireless device.

28. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for obtaining an explicit indication whether a record        of treating a medical condition in the first individual with a        particular protocol contains any extrinsic evidence that        treating the medical condition with the particular protocol has        precedent.

29. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for initiating a telephone call between the first        individual and another entity as an automatic response to the        first individual not being compliant with a health regimen and        to an indication that the other entity is available.

30. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for signaling a decision whether to transfer a        resource to the first individual partly based on an indication        that the first individual is not compliant with a health regimen        and partly based on an indication that the first individual has        accepted a telephone call.

31. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for causing a locally-resident subscriber registry to        be updated with an indication of the first individual.

32. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for determining whether a medical device is in a        vicinity of another device, the other device being the device        associated with the first individual.

33. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for responding to an event with an audible        notification, the event being the wearable article at the first        care facility being configured to indicate the second data        component received from the first individual after the first        individual received the playable prompt that was automatically        selected according to the first data.

34. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for responding to a payment-reduction event relating        to a first medical treatment by causing a selective retrieval of        one or more records that lack any prominence indication relating        to the first medical treatment from an archive that includes at        least one prominence indication relating to a second medical        treatment.

35. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for detecting a passive wireless transponder within a        vicinity of a vehicle, the wearable article including the        passive wireless transponder.

36. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for obtaining the second data component, the second        data component including an indication whether or not the first        individual is compliant with a first health regimen.

37. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for triggering a search of a particular records        archive by providing a selective search criterion, one that        results in an exclusion of a first element in the particular        records archive and an inclusion of a second element in the        particular records archive, the second element referring to the        first individual or to a patient of the first individual.

38. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for transmitting a real-time notification to another        entity as an automatic response to an interface on or near the        first individual detecting a particular event relating to the        first individual.

39. The healthcare information management system of any of the aboveSYSTEM CLAUSES, further comprising:

the transistor-based circuitry having the event-sequencing structureconfigured for causing the wearable article at the first care facilityto indicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual including at least

-   -   transistor-based circuitry having an event-sequencing structure        configured for implementing a failsafe preventing medical        equipment from operating until an order that associates the        medical equipment with the first individual is received and        until an indication is received that the first individual is in        a vicinity of the medical equipment.

40. (Independent) A healthcare information management method comprising:causing a first individual to receive a playable prompt that wasautomatically selected according to a first data component received fromthe first individual;

receiving a second data component from the first individual after thefirst individual received the playable prompt that was automaticallyselected according to the first data component received from the firstindividual; and

invoking transistor-based circuitry having an event-sequencing structureconfigured for causing a wearable article at a first care facility toindicate the second data component received from the first individualafter the first individual received the playable prompt that wasautomatically selected according to the first data component receivedfrom the first individual.

41. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   looking up a communication delay as a function of a therapeutic        protocol associated with a recipient of the therapeutic        protocol, the recipient being or not being the first individual;        and    -   transmitting a query as an automatic response to an expiration        of the communication delay.

42. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   looking up a communication delay as a function of a medical        condition associated with a recipient of the wearable article,        the recipient being or not being the first individual; and    -   transmitting a query as an automatic response to an expiration        of the communication delay.

43. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   causing an individual to be contacted by a fallback mode of        communication as a conditional response to receiving no reply        from the individual by a prior mode of communication, the prior        mode of communication being telephonic, the individual being the        first individual or a patient of the first individual.

44. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   contacting an individual by a fallback mode of communication as        an automatic and conditional response to receiving no reply from        the individual by a prior mode of communication, the fallback        mode of communication being telephonic, the individual being the        first individual or a patient of the first individual.

45. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   updating a locally-resident subscriber registry in response to        the first individual entering a service zone.

46. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   obtaining an indication that a specific pathology in the first        individual has been treated at a first hospital and an        indication that the specific pathology in the first individual        has been treated at a second hospital, the first care facility        being the first hospital.

47. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   retrieving a medical treatment record of the first individual        selectively in response to an explicit indication of a payment        reduction that identifies the first individual.

48. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   retrieving a medical treatment record relating to a set of one        or more pathologies selectively in response to an explicit        indication of a payment reduction that identifies the set.

49. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   detecting a wireless device within an effective range of a        stationary device, the wearable article being the wireless        device.

50. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   obtaining an explicit indication whether a record of treating a        medical condition in the first individual with a particular        protocol contains any extrinsic evidence that treating the        medical condition with the particular protocol has precedent.

51. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   initiating a telephone call between the first individual and        another entity as an automatic response to the first individual        not being compliant with a health regimen and to an indication        that the other entity is available.

52. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   signaling a decision whether to transfer a resource to the first        individual partly based on an indication that the first        individual is not compliant with a health regimen and partly        based on an indication that the first individual has accepted a        telephone call.

53. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   causing a locally-resident subscriber registry to be updated        with an indication of the first individual.

54. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   determining whether a medical device is in a vicinity of another        device, the other device being the device associated with the        first individual.

55. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   responding to an event with an audible notification, the event        being the wearable article at the first care facility being        configured to indicate the second data component received from        the first individual after the first individual received the        playable prompt that was automatically selected according to the        first data.

56. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   responding to a payment-reduction event relating to a first        medical treatment by causing a selective retrieval of one or        more records that lack any prominence indication relating to the        first medical treatment from an archive that includes at least        one prominence indication relating to a second medical        treatment.

57. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   detecting a passive wireless transponder within a vicinity of a        vehicle, the wearable article including the passive wireless        transponder.

58. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   obtaining the second data component, the second data component        including an indication whether or not the first individual is        compliant with a first health regimen.

59. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   triggering a search of a particular records archive by providing        a selective search criterion, one that results in an exclusion        of a first element in the particular records archive and an        inclusion of a second element in the particular records archive,        the second element referring to the first individual or to a        patient of the first individual.

60. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   transmitting a real-time notification to another entity as an        automatic response to an interface on or near the first        individual detecting a particular event relating to the first        individual.

61. The healthcare information management system of any of the aboveMETHOD CLAUSES, further comprising:

the invoking the transistor-based circuitry having the event-sequencingstructure configured for causing the wearable article at the first carefacility to indicate the second data component received from the firstindividual after the first individual received the playable prompt thatwas automatically selected according to the first data componentreceived from the first individual including at least

-   -   implementing a failsafe preventing medical equipment from        operating until an order that associates the medical equipment        with the first individual is received and until an indication is        received that the first individual is in a vicinity of the        medical equipment.

62. (Independent) A healthcare information management method comprising:

obtaining an association between data indicating a current health statusof a first individual and a record designator; and

causing a wearable article at a first care facility to include the dataindicating the current health status of the first individual as anautomatic and conditional response to local input at the first carefacility matching the record designator.

63. The healthcare information management method of CLAUSE 62 furthercomprising:

performing the operation(s) of any one or more of the above METHODCLAUSES that depend from METHOD CLAUSE 40.

64. (Independent) A healthcare information management method comprising:

obtaining an indication via a first device local to a first individualthat the first individual is noncompliant with a first health regimen;

obtaining an indication via a second device that a second individual isavailable to participate in an electronic intercommunication; and

signaling the electronic intercommunication as an automatic andconditional response to the indication via the first device local to thefirst individual that the first individual is noncompliant with thefirst health regimen and to the indication via the second device thatthe second individual is available to participate in the electronicintercommunication.

65. The healthcare information management method of CLAUSE 64 furthercomprising:

performing the operation(s) of any one or more of the above METHODCLAUSES that depend from METHOD CLAUSE 40.

66. (Independent) A healthcare information management method comprising:

obtaining via a first device a scalar indication of how well a firsthealth regimen has been followed by a first individual;

obtaining via a second device a scalar indication of how well a secondhealth regimen has been followed by a second individual; and

characterizing a performance of a third individual with a scalarevaluation obtained by mathematically combining the scalar indication ofhow well the first health regimen has been followed by the firstindividual with the scalar indication of how well the second healthregimen has been followed by the second individual.

67. The healthcare information management method of CLAUSE 66 furthercomprising:

performing the operation(s) of any one or more of the above METHODCLAUSES that depend from METHOD CLAUSE 40.

68. (Independent) A healthcare information management method comprising:

obtaining a field of view within which a specific portion of the fieldof view includes a view of a first patient;

obtaining user input selectively indicating the first patient byidentifying the specific portion that depicts the first patient; and

signaling medical data about the first patient as an automatic andconditional response to the user input selectively indicating the firstpatient by identifying the specific portion that depicts the firstpatient.

69. The healthcare information management method of CLAUSE 68 furthercomprising:

performing the operation(s) of any one or more of the above METHODCLAUSES that depend from METHOD CLAUSE 40.

70. (Independent) A healthcare information management method comprising:

causing a first individual to receive a playable prompt that wasautomatically selected according to a first data component received fromthe first individual;

receiving a second data component from the first individual after thefirst individual received the playable prompt that was automaticallyselected according to the first data component received from the firstindividual; and

causing a wearable article at a first care facility to indicate thesecond data component received from the first individual after the firstindividual received the playable prompt that was automatically selectedaccording to the first data component received from the firstindividual.

71. The healthcare information management method of CLAUSE 70 furthercomprising:

performing the operation(s) of any one or more of the above METHODCLAUSES that depend from METHOD CLAUSE 40.

72. (Independent) A healthcare information management method comprising:

obtaining a first indication whether or not a first patient has violateda first health regimen;

obtaining a second indication whether or not the first patient hasviolated the first health regimen;

signaling a decision whether or not to initiate an electroniccommunication between the first patient and a provider as an automaticand conditional response to the first indication whether or not thefirst patient has violated the first health regimen but not to thesecond indication whether or not the first patient has violated thefirst health regimen; and

signaling a decision whether or not to route the provider to the firstpatient as a conditional response to the first indication whether or notthe first patient has violated the first health regimen and to thesecond indication whether or not the first patient has violated thefirst health regimen.

73. The healthcare information management method of CLAUSE 72 furthercomprising:

performing the operation(s) of any one or more of the above METHODCLAUSES that depend from METHOD CLAUSE 40.

74. (Independent) A healthcare information management method comprising:

assigning a component of an artificial incentive to a first patientpartly based on an indication that the first patient has been admittedto a first institution in relation to a particular condition and partlybased on an indication that the first patient has not undergone aninstitutional readmission; and

transmitting to the first patient a result of assigning the component ofthe artificial incentive to the first patient partly based on theindication that the first patient has been admitted to the firstinstitution in relation to the particular condition and partly based onthe indication that the first patient has not undergone theinstitutional readmission.

75. The healthcare information management method of CLAUSE 74 furthercomprising:

performing the operation(s) of any one or more of the above METHODCLAUSES that depend from METHOD CLAUSE 40.

76. (Independent) A healthcare information management method comprising:

obtaining an indication that an order associates a first patient with amedical device;

obtaining an indication that the medical device is in a vicinity of thefirst patient; and

enabling the medical device conditionally, partly based on theindication that the order associates the first patient with the medicaldevice and partly based on the indication that the medical device is inthe vicinity of the first patient.

77. The healthcare information management method of CLAUSE 76 furthercomprising:

performing the operation(s) of any one or more of the above METHODCLAUSES that depend from METHOD CLAUSE 40.

78. (Independent) A healthcare information management method comprising:

identifying a first health regimen associated with a first individual,the first health regimen including one or more healthcare-related tasksassociated with a time interval;

causing a countdown timer to indicate a remaining portion of the timeinterval associated with the one or more healthcare-related tasksvisibly in a vicinity of the first individual; and

signaling a Boolean indication of whether or not any of the one or morehealthcare-related tasks associated with the time interval wereperformed within the time interval after the countdown timer hasindicated the remaining portion of the time interval associated with theone or more healthcare-related tasks visibly in the vicinity of thefirst individual.

79. The healthcare information management method of CLAUSE 78 furthercomprising:

performing the operation(s) of any one or more of the above METHODCLAUSES that depend from METHOD CLAUSE 40.

80. (Independent) A healthcare information management method comprising:

causing an electronic record of a first protocol for a particularcondition to be annotated with a scan of a document; and

retrieving the electronic record of the first protocol after theelectronic record of the first protocol is annotated with the scan ofthe document partly based on an indication of a first patient undergoingthe first protocol and partly based on an indication of an institutionalreadmission.

81. The healthcare information management method of CLAUSE 80 furthercomprising:

performing the operation(s) of any one or more of the above METHODCLAUSES that depend from METHOD CLAUSE 40.

82. (Independent) A healthcare information management method comprising:

obtaining an indication that a particular condition was treated in afirst patient with a first protocol;

causing a record of a second patient to include the indication that theparticular condition was treated in the first patient with the firstprotocol; and

retrieving the record of the second patient selectively in response toan association between the second patient and an indication of aninstitutional readmission after the record of the second patientincludes the indication that the particular condition was treated in thefirst patient with the first protocol.

83. The healthcare information management method of CLAUSE 82 furthercomprising:

performing the operation(s) of any one or more of the above METHODCLAUSES that depend from METHOD CLAUSE 40.

84. (Independent) A healthcare information management method comprising:

obtaining an indication of a first protocol being employed in relationto a particular condition in a first patient;

requesting an effectiveness indication of the first protocol from anentity partly based on the entity validating the first protocol andpartly based on a first communication delay associated with the firstprotocol, the first communication delay exceeding one hour; and

signaling a decision whether to update a prominence indication of thefirst protocol in response to whether the effectiveness indication ofthe first protocol was received from the entity after the effectivenessindication is requested from the entity partly based on the entityvalidating the first protocol and partly based on the firstcommunication delay associated with the first protocol.

85. The healthcare information management method of CLAUSE 84 furthercomprising:

performing the operation(s) of any one or more of the above METHODCLAUSES that depend from METHOD CLAUSE 40.

86. (Independent) A healthcare information management method comprising:

obtaining an association between a particular condition and a firstprotocol;

causing a comparison between a threshold and a prominence indication oftreating the particular condition with the first protocol after theassociation between then particular condition and the first protocol isobtained; and

signaling a decision whether to caution a caregiver partly based on theassociation between the particular condition and the first protocol andpartly based on the comparison between the threshold and the prominenceindication of treating the particular condition with the first protocol.

87. The healthcare information management method of CLAUSE 86 furthercomprising:

performing the operation(s) of any one or more of the above METHODCLAUSES that depend from METHOD CLAUSE 40.

88. (Independent) A healthcare information management method comprising:

obtaining an association between a care administration space and a firstdevice;

obtaining via a second device a patient consent conditionallyauthorizing a release of a first medical record, the second device beinga mobile device; and

causing the first device to receive the first medical record partlybased on the second device entering the care administration space andpartly based on the patient consent authorizing the release of the firstmedical record.

89. The healthcare information management method of CLAUSE 88 furthercomprising:

performing the operation(s) of any one or more of the above METHODCLAUSES that depend from METHOD CLAUSE 40.

90. (Independent) A healthcare information management method comprising:

obtaining an indication of a first device associated with and wearableby a patient hospitalized for a particular condition;

obtaining an indication of a second device associated with and wearableby a caregiver;

causing a recordation of a timestamp as an automatic response to thefirst device associated with and wearable by the patient and the seconddevice associated with and wearable by a caregiver both being in asingle common location; and

describes causing a retrieval of the timestamp in response to anindication of an institutional readmission after the recordation of thetimestamp indicating the first device associated with and wearable bythe patient and the second device associated with and wearable by thecaregiver both having been in the single common location.

91. The healthcare information management method of CLAUSE 90 furthercomprising:

performing the operation(s) of any one or more of the above METHODCLAUSES that depend from METHOD CLAUSE 40.

92. (Independent) A system comprising:

means for performing the operation(s) of any one or more of the aboveMETHOD CLAUSES.

93. (Independent) An article of manufacture comprising:

one or more physical media configured to bear a device-detectableimplementation of a method including at least

causing a first individual to receive a playable prompt that wasautomatically selected according to a first data component received fromthe first individual;

receiving a second data component from the first individual after thefirst individual received the playable prompt that was automaticallyselected according to the first data component received from the firstindividual; and

causing a wearable article at a first care facility to indicate thesecond data component received from the first individual after the firstindividual received the playable prompt that was automatically selectedaccording to the first data component received from the firstindividual.

94. The article of manufacture of CLAUSE 93 in which a portion of theone or more physical media comprises:

one or more signal-bearing media configured to transmit a binarysequence manifesting one or more device-executable instructionsconfigured to perform the operation(s) of any one or more of the aboveMETHOD CLAUSES.

95. (Independent) An article of manufacture comprising:

one or more physical media bearing a device-detectable outputmanifesting an occurrence of

causing a first individual to receive a playable prompt that wasautomatically selected according to a first data component received fromthe first individual;

receiving a second data component from the first individual after thefirst individual received the playable prompt that was automaticallyselected according to the first data component received from the firstindividual; and

causing a wearable article at a first care facility to indicate thesecond data component received from the first individual after the firstindividual received the playable prompt that was automatically selectedaccording to the first data component received from the firstindividual.

96. The article of manufacture of CLAUSE 95 in which a portion of theone or more physical media comprises:

one or more signal-bearing media bearing at least one binary sequencefrom an event-sequencing structure configured to perform theoperation(s) of any one or more of the above METHOD CLAUSES.

All of the patents and other publications referred to above areincorporated herein by reference generally—including those identified inrelation to particular new applications of existing techniques—to theextent not inconsistent herewith (in each respective latest edition,where applicable). While various system, method, article of manufacture,or other embodiments or aspects have been disclosed above, also, othercombinations of embodiments or aspects will be apparent to those skilledin the art in view of the above disclosure. The various embodiments andaspects disclosed above are for purposes of illustration and are notintended to be limiting, with the true scope and spirit being indicatedin the final claim set that follows.

What is claimed is:
 1. A system, comprising: circuitry for receiving atleast one input from at least one personal communication deviceassociated with at least one device identifier, the at least one inputindicative of the at least one personal communication device entering aservice zone; circuitry for associating the at least one personalcommunication device with a particular patient identifier based at leastpartly on the circuitry for receiving the at least one input from the atleast one personal communication device associated with the at least onedevice identifier; circuitry for selecting a playable prompt, theselected playable prompt including at least one of audio, image, orvideo content, based at least partly on the circuitry for associatingthe at least one personal communication device with the particularpatient identifier; circuitry for causing the selected playable promptto be output in a manner perceivable by a particular patient associatedwith the particular patient identifier; circuitry for obtaining medicalintake data including at least one indication of at least one of speechor appearance of the particular patient subsequent to the causing theselected playable prompt to be output; circuitry for detecting medicallyrelevant data related to the particular patient from the at least oneindication of the at least one of speech or appearance of the particularpatient; circuitry for causing the at least one personal communicationdevice to display at least one detectable structure, the at least onedetectable structure including at least one encoding associated with atleast some of the obtained medical intake data; and circuitry forimplementing a failsafe preventing medical equipment from operatinguntil an indication is received from electronic detection that the atleast one personal communication device associated with the at least onedevice identifier associated with the particular patient identifier isin a vicinity of the medical equipment and until the display of the atleast one detectable structure is recognized by a detection deviceoperably coupled with the medical equipment.
 2. The system of claim 1,wherein the circuitry for causing the at least one personalcommunication device to display at least one detectable structure, theat least one detectable structure including at least one encodingassociated with at least some of the obtained medical intake datareceived from the particular patient comprises: circuitry for causingthe at least one personal communication device to display a barcodeconfigured to indicate the at least some of the obtained medical intakedata.
 3. The system of claim 1, further comprising: circuitry forupdating a locally-resident subscriber registry based at least partly onthe at least one input indicative of the at least one personalcommunication device entering the service zone.
 4. An article ofmanufacture, comprising: at least one non-transitory computer-readablemedium including at least: one or more instructions for receiving atleast one input from at least one personal communication deviceassociated with at least one device identifier, the at least one inputindicative of the at least one personal communication device entering aservice zone; one or more instructions for associating the at least onepersonal communication device with a particular patient identifier basedat least partly on the one or more instructions for receiving the atleast one input from the at least one personal communication deviceassociated with the at least one device identifier; one or moreinstructions for selecting a playable prompt, the selected playableprompt including at least one of audio, image, or video content, basedat least partly on the one or more instructions for associating the atleast one personal communication device with the particular patientidentifier; one or more instructions for causing the selected playableprompt to be output in a manner perceivable by a particular patientassociated with the particular patient identifier; one or moreinstructions for obtaining medical intake data including at least oneindication of at least one of speech or appearance of the particularpatient subsequent to the causing the selected playable prompt to beoutput; one or more instructions for detecting medically relevant datarelated to the particular patient from the at least one indication ofthe at least one of speech or appearance of the particular patient; oneor more instructions for causing the at least one personal communicationdevice to display at least one detectable structure, the at least onedetectable structure including at least one encoding associated with atleast some of the obtained medical intake data and one or moreinstructions for implementing a failsafe preventing medical equipmentfrom operating until an indication is received from electronic detectionthat the at least one personal communication device associated with theat least one device identifier associated with the particular patientidentifier is in a vicinity of the medical equipment and until thedisplay of the at least one detectable structure is recognized by adetection device operably coupled with the medical equipment.
 5. Thesystem of claim 1, wherein the circuitry for receiving at least oneinput from at least one personal communication device associated with atleast one device identifier, the at least one input indicative of the atleast one personal communication device entering a service zonecomprises: circuitry for detecting that a smartphone associated with theat least one device identifier has established a wireless connectionwith a stationary device associated with the service zone; and whereinthe circuitry for associating the at least one personal communicationdevice with a particular patient identifier based at least partly on thecircuitry for receiving the at least one input from the at least onepersonal communication device associated with the at least one deviceidentifier includes at least: circuitry for identifying the particularpatient identifier based at least partly on the at least one deviceidentifier.
 6. The system of claim 1, further comprising: circuitry forobtaining an explicit indication whether a record of treating theparticular patient for a medical condition with a particular protocolcontains any extrinsic evidence that treating the medical condition withthe particular protocol has precedent.
 7. The system of claim 1, furthercomprising: circuitry for initiating a telephone call between theparticular patient and another entity as an automatic response to theparticular patient not being compliant with a health regimen based atleast partly on the circuitry for obtaining medical intake dataincluding at least one indication of at least one of speech orappearance of the particular patient.
 8. The system of claim 1, furthercomprising: circuitry for signaling a decision whether to transfer aresource to the particular patient based at least partly on anindication that the particular patient is not compliant with a healthregimen and based at least partly on an indication that the particularpatient has accepted a telephone call relating to a particular timedadministration of a particular treatment specified by the healthregimen.
 9. The system of claim 1, wherein the circuitry for associatingthe at least one personal communication device with a particular patientidentifier based at least partly on the circuitry for receiving the atleast one input from the at least one personal communication deviceassociated with the at least one device identifier comprises: circuitryfor causing a locally-resident subscriber registry to be updated with anindication that the particular patient has entered a service zone basedat least partly on an inference that the at least one personalcommunication device is possessed by the particular patient and based atleast partly on an identification of the particular patient using the atparticular patient identifier.
 10. The system of claim 1, wherein thecircuitry for receiving at least one input from at least one personalcommunication device associated with at least one device identifier, theat least one input indicative of the at least one personal communicationdevice entering a service zone comprises: circuitry for detecting thatthe at least one personal communication device is within a particularvicinity of a medical device associated with the service zone.
 11. Thesystem of claim 1, further comprising: circuitry for providing anaudible notification as a substantially real-time notification to adevice at a care facility, the device at the care facility configured toalert upon detection of medically relevant data.
 12. The system of claim1, wherein the circuitry for obtaining medical intake data including atleast one indication of at least one of speech or appearance of theparticular patient subsequent to the causing the selected playableprompt to be output comprises: circuitry for causing one or more of atleast one microphone or at least one image sensor of the at least onepersonal device to capture one or more of at least some audio or atleast some video data as the medical intake data; and circuitry fordetecting the at least one indication of at least one of speech orappearance of the particular patient from within the one or more of atleast some audio data or at least some video data.
 13. The system ofclaim 1, further comprising: circuitry for transmitting a substantiallyreal-time notification to at least one other entity as an automaticresponse to an interface on or near the particular patient detecting aparticular event relating to the particular patient.
 14. The system ofclaim 1, wherein the circuitry for implementing a failsafe preventingmedical equipment from operating until an indication is received fromelectronic detection that the at least one personal communication deviceassociated with the at least one device identifier associated with theparticular patient identifier is in a vicinity of the medical equipmentand until the display of the at least one detectable structure isrecognized by a detection device operably coupled with the medicalequipment comprises: circuitry for enabling the medical equipment tofunction only after receiving an indication of a barcode having beenscanned, the barcode configured to indicate at least some of theobtained medical intake data.
 15. The system of claim 1, furthercomprising: circuitry for transmitting a message causing an audiblenotification to be output as a substantially real-time notification. 16.The system of claim 1, wherein the circuitry for obtaining medicalintake data including at least one indication of at least one of speechor appearance of the particular patient subsequent to the causing theselected playable prompt to be output comprises: circuitry for receivingat least one spoken word input from the particular patient via the atleast one personal communication device.
 17. The system of claim 1,wherein the circuitry for causing the selected playable prompt to beoutput in a manner perceivable by a particular patient associated withthe particular patient identifier comprises: circuitry for playing atleast one of an audio, image or video prompt that was automaticallyselected based at least partly on the circuitry for associating the atleast one personal communication device with the particular patientidentifier, the playable prompt configured to a particular conditionassociated with the particular patient associated with the particularpatient identifier.
 18. The system of claim 1, wherein the circuitry forobtaining medical intake data including at least one indication of atleast one of speech or appearance of the particular patient subsequentto the causing the selected playable prompt to be output comprises:circuitry for capturing at least one of a spoken word input from theparticular patient, an image input representing the particular patient,a video input representing the particular patient, or a touch input fromthe particular patient as the obtained medical intake data.
 19. Thesystem of claim 1, wherein the circuitry for causing the at least onepersonal communication device to display at least one detectablestructure, the at least one detectable structure including at least oneencoding associated with at least some of the obtained medical intakedata comprises: circuitry for causing the at least one personalcommunication device to display a barcode configured to indicate the atleast some of the obtained medical intake data.
 20. The system of claim1, wherein the circuitry for causing the at least one personalcommunication device to display at least one detectable structure, theat least one detectable structure including at least one encodingassociated with at least some of the obtained medical intake datacomprises: circuitry for encoding the at least some of the obtainedmedical intake data in at least one transponder of the at least onepersonal communication device.
 21. The system of claim 1, wherein thecircuitry for implementing a failsafe preventing medical equipment fromoperating until an order that associates the medical equipment with theparticular patient is received and until an indication is received fromelectronic detection that the at least one personal communication deviceassociated with the at least one device identifier associated with theparticular patient identifier is in a vicinity of the medical equipmentcomprises: circuitry for enabling the medical equipment to function onlyafter a detection module proximate to the medical equipment detects apresence of the at least one personal communication device associatedwith the at least one device identifier associated with the particularpatient identifier.
 22. A method, comprising: receiving at least oneinput from at least one personal communication device associated with atleast one device identifier, the at least one input indicative of the atleast one personal communication device entering a service zone;associating the at least one personal communication device with aparticular patient identifier based at least partly on the receiving theat least one input from the at least one personal communication deviceassociated with the at least one device identifier; selecting a playableprompt, the selected playable prompt including at least one of audio,image, or video content, based at least partly on the associating the atleast one personal communication device with the particular patientidentifier; causing the selected playable prompt to be output in amanner perceivable by a particular patient associated with theparticular patient identifier; obtaining medical intake data includingat least one indication of at least one of speech or appearance of theparticular patient subsequent to the causing the selected playableprompt to be output; detecting medically relevant data related to theparticular patient from the at least one indication of the at least oneof speech or appearance of the particular patient; causing the at leastone personal communication device to display at least one detectablestructure, the at least one detectable structure including at least oneencoding associated with at least some of the obtained medical intakedata; and implementing a failsafe preventing medical equipment fromoperating until an indication is received from electronic detection thatthe at least one personal communication device associated with the atleast one device identifier associated with the particular patientidentifier is in a vicinity of the medical equipment and until thedisplay of the at least one detectable structure is recognized by adetection device operably coupled with the medical equipment, whereinthe receiving, associating, selecting, causing, obtaining, detecting,and implementing are at least partly implemented using at least oneprocessing device.
 23. The system of claim 1, wherein the circuitry forassociating the at least one personal communication device with aparticular patient identifier based at least partly on the circuitry forreceiving the at least one input from the at least one personalcommunication device associated with the at least one device identifiercomprises: circuitry for associating the at least one device identifierwith at least one medical record, the at least one medical recordassociated with at least one identity of at least one particularpatient.
 24. The system of claim 1, wherein the circuitry for obtainingmedical intake data including at least one indication of at least one ofspeech or appearance of the particular patient subsequent to the causingthe selected playable prompt to be output comprises: circuitry foridentifying at least one medical condition previously associated withthe at least one particular patient; and circuitry for detecting atleast one symptom associated with the identified at least one medicalcondition based at least partly on the at least one of speech orappearance of the particular patient.
 25. The system of claim 24,wherein the circuitry for detecting at least one symptom associated withthe identified at least one medical condition based at least partly onthe at least one of speech or appearance of the particular patientcomprises: circuitry for detecting biometric data associated with the atleast one symptom.
 26. The system of claim 1, wherein the circuitry forcausing the at least one personal communication device to display atleast one detectable structure, the at least one detectable structureincluding at least one encoding associated with at least some of theobtained medical intake data comprises: circuitry configured forgenerating a barcode based at least partly on the at least some of theobtained medical intake data; and circuitry configured for transmittingthe generated barcode to the at least one personal communication device,the transmitted barcode configured for display on the at least onepersonal communication device.
 27. The system of claim 1, wherein thecircuitry for receiving at least one input from at least one personalcommunication device associated with at least one device identifier, theat least one input indicative of the at least one personal communicationdevice entering a service zone comprises: circuitry configured fordetecting that the at least one personal communication device is withinan effective range of at least one wireless transceiver associated withthe service zone.
 28. The system of claim 1, wherein the circuitry forreceiving at least one input from at least one personal communicationdevice associated with at least one device identifier, the at least oneinput indicative of the at least one personal communication deviceentering a service zone comprises: circuitry configured for detectingthat at least one of a personal smartphone or a tablet computer as theat least one personal communication device has entered the service zone.29. The system of claim 1, wherein the circuitry for associating the atleast one personal communication device with a particular patientidentifier based at least partly on the circuitry for receiving the atleast one input from the at least one personal communication deviceassociated with the at least one device identifier comprises: circuitryfor associating the particular patient identifier with the at least onepersonal communication device based at least partly on at least oneapplication running on the at least one personal communication device.30. The system of claim 1, wherein the circuitry for causing the atleast one personal communication device to display at least onedetectable structure, the at least one detectable structure including atleast one encoding associated with at least some of the obtained medicalintake data comprises: circuitry for transmitting the at least onedetectable structure to the at least one personal communication devicein a device-readable format.
 31. The system of claim 1, wherein thecircuitry for causing the selected playable prompt to be output in amanner perceivable by a particular patient associated with theparticular patient identifier comprises: circuitry for transmitting theselected playable prompt to the at least one personal communicationdevice in a device-playable format.
 32. The system of claim 1, whereinthe circuitry for obtaining medical intake data including at least oneindication of at least one of speech or appearance of the particularpatient subsequent to the causing the selected playable prompt to beoutput comprises: circuitry for presenting a user interface on thepersonal communication device, the user interface configured to receiveuser input responsive to a request for the medical intake data conveyedby the selected playable prompt.
 33. The system of claim 1, wherein thecircuitry for obtaining medical intake data including at least oneindication of at least one of speech or appearance of the particularpatient subsequent to the causing the selected playable prompt to beoutput comprises: circuitry for receiving a patient consent conveyed byan utterance of the particular patient included in the at least oneindication of at least one of speech or appearance of the particularpatient.
 34. The system of claim 33, wherein the circuitry for receivinga patient consent conveyed by an utterance of the particular patientincluded in the at least one indication of at least one of speech orappearance of the particular patient comprises: circuitry for receivinga patient consent for at least one of performance of a medical procedureor release of a medical record conveyed by the utterance of theparticular patient included in the at least one indication of at leastone of speech or appearance of the particular patient.
 35. The system ofclaim 1, wherein the circuitry for receiving at least one input from atleast one personal communication device associated with at least onedevice identifier, the at least one input indicative of the at least onepersonal communication device entering a service zone comprises:circuitry for receiving at least some GPS data from the at least onepersonal communication device associated with at least one deviceidentifier, the at least some GPS data one input indicative of aproximity of the at least one personal communication device to theservice zone.
 36. The system of claim 1, further comprising: circuitryfor causing the at least one personal communication device to display anindication of an availability of an artificial incentive for receipt bythe particular patient upon a manifestation of an improvement in acondition associated with the individual indicated by the detectedmedically relevant data.
 37. The system of claim 1, wherein thecircuitry for receiving at least one input from at least one personalcommunication device associated with at least one device identifier, theat least one input indicative of the at least one personal communicationdevice entering a service zone comprises: circuitry for receiving atleast one input from at least one device wearable by a patienthospitalized for a particular condition, the at least one inputindicative of the at least one device wearable by the patienthospitalized for the particular condition entering a service zone;circuitry for receiving at least one input from at least one devicewearable by a caregiver, the at least one input indicative of the atleast one device wearable by the caregiver entering the service zone;and circuitry for initiating a timestamp as an automatic response to theboth the at least one device wearable by the patient hospitalized forthe particular condition and the at least one device wearable by thecaregiver being in a single common location.
 38. The system of claim 1,wherein the associating the at least one personal communication devicewith a particular patient identifier based at least partly on thecircuitry for receiving the at least one input from the at least onepersonal communication device associated with the at least one deviceidentifier comprises: circuitry for triggering a search of a particularrecords archive by providing the at least one device identifier as aselective search criterion, one that results in the particular patientidentifier being returned by the search of the particular recordsarchive.